Common failures
Troubleshooting
What to check when SDK calls, uploads, analytics, comments, or reports do not work.
SDK calls return unavailable
unavailable usually means Firebase, login, or the host bridge is not ready. The game should keep running and show a soft fallback.
For local prototypes, confirm the game is loaded inside a Qubiz host page and targetOrigin matches the host origin.
- Check QubizSDK.configure targetOrigin.
- Check that the player is signed in for write operations.
- Check that the required permission scope is granted.
- Check browser console messages from the host page.
Upload or publish fails
Most upload failures come from a missing build ZIP, over-large files, incomplete legal attestations, invalid manifest fields, or requested SDK scopes that are not supported.
- Use the upload wizard with a real account, not a guest session.
- Keep the build ZIP under 100 MB.
- Use only valid requestedScopes.
- Submit as a draft and respond to review messages if changes are requested.
- If a public page does not appear in the sitemap, confirm status is published.