Help

Objective diagnosis, without guessing.

Use the HTTP status and response message to determine the next step.

Common situations

The first preview took longer

The first request of the day can encounter a cold start. The interface warns that generation can take up to roughly 40 seconds; wait for the session or generate it again if it expires.

I received 401 from the API

Send a valid Bearer JWT or X-API-Key to endpoints that accept API keys. Missing or invalid keys return 401.

I received 402 when starting a build

The monthly free quota has been reached and there is no active plan or credit balance. Check the wallet or start checkout/top-up.

I received 422 when creating a build

Check that the app has a manifest containing app_name and primary_color. Invalid formats and required fields also return 422.

My push notification did not arrive

Check the device, token, and channel. FCM infrastructure is integrated, but physical-device end-to-end delivery verification is still pending.

Apple or Google rejected publication

The terms documentation is under review. The proposed flow corrects eligible issues and resubmits within the same request; customer content and missing data can fall outside coverage.

Recurring codes

400Duplicate or invalid input, such as an existing package name or slug.

401Missing authentication, invalid JWT, or invalid API key.

403Credential cannot access the resource or lacks the owner role.

404An app, bundle, channel, build, preview, or other resource was not found.

409Import conflict, such as an existing package name.

422Invalid required field, format, manifest, or business rule.

429Preview, chat, update, or build limit was reached.

503A billing or push dependency is not configured in the environment.