Dart SDK

Match your code to the API exported by the installed version. A successful package installation does not establish managed-runtime credentials, project access or a working provider connection.

Verify account, tenant, project and environment access for each service operation. Treat 401 as authentication failure and 403 as denied scope or project access. Investigate failed mutations before submitting them again; do not assume they were never saved.

Managed experience uses durable PostgreSQL storage on development and production. Data is isolated by tenant, project and player. A new player starts with an empty profile, inventory, cloud save and sessions. Inventory grant and consume require an idempotencyKey; attempts to overspend return HTTP 409. Give the machine client experience:read and experience:write for the complete experience workflow. This managed-service behavior does not turn local sample adapters into durable storage.

The managed streaming implementation supports DartStream Core. External broker connectivity is not provided by that implementation.

Never embed a client secret in browser JavaScript, a mobile binary or Flutter --dart-define values. Use your own trusted backend to verify the player’s Firebase ID token and derive the player ID. Expose narrow game operations rather than a generic service proxy.

See the game authentication contract for the account boundary. A configured application backend is required; there is no enabled public-client grant.