Skip to main content

​
Submissions

Submissions help you move from internal development to a publicly available app across supported miniapp platforms. When you submit, UptopiaKit reviews your app’s readiness, validates policy compliance, and coordinates deployment using our infrastructure and platform integrations.

​
When to submit

Create a submission after you have completed Development and Testing, filled in required metadata, and verified your app is production-ready.

​
Prerequisites (read carefully)

Your app must meet all of the following before you can submit:
  • Manifest Settings: fill in all required fields. Optional fields are encouraged for a higher‑quality and more discoverable manifest.
  • Production version: you must have exactly one version set to Production to submit.
  • Policy compliance: ensure your app has no policy violations.
  • App status: the app must be Active. Inactive apps cannot run versions or be submitted.
If any prerequisite is missing, your submission cannot proceed.

​
Key constraints

  • One submission per version per app at a time. You cannot create multiple submissions targeting the same version concurrently.
  • Cancel only when Pending. Users can cancel a submission request only while its status is Pending (just created).
  • Locked during In‑Review. When a submission is In‑Review, UptopiaKit is evaluating your app; the submission status and the associated version’s Production state cannot be changed during this time.

​
Snapshot at creation (important)

When you create a submission, UptopiaKit snapshots all relevant app data — including settings, App Events, IAPs, and more — and attaches it to the submission. This snapshot is what our team reviews.
  • Changes you make after submission creation are not included in the current review.
  • Updates will be considered only in a new submission. Therefore, verify thoroughly, test completely, and ensure you are ready before submitting to avoid extra back‑and‑forth.

​
Submission lifecycle and statuses

  1. Pending — You created the submission. You may cancel at this stage.
  2. In‑Review — UptopiaKit team is reviewing, testing, and verifying readiness and compliance. The submission and its version’s Production state are locked.
  3. Decision — One of:
    • Approved — Your app passes review. UptopiaKit will begin deployment.
    • Rejected — Your app did not pass review. You’ll receive clear feedback on the reasons and how to resolve them. Feedback may be updated over time — please check the submission thread.
  4. Deploying (after Approved) — UptopiaKit is configuring and deploying your app to become public.
  5. Published — Deployment completed successfully. Your app is now publicly accessible to end users via supported platforms.
Notes:
  • Only a Released version is visible to the public. After approval and deployment, your Production version becomes Released.
  • If you want to submit a new version later, set that version to Production, then create a new submission.

​
Review timeline and communication

  • Typical review time: 5–20 days from submission creation.
  • During review, the UptopiaKit team may reach out via support channels or your account email to request additional information.
  • You can contact us anytime through support if you have questions.

​
Tier and limits

UptopiaKit provides the infrastructure and publishing workflow, with some limits that vary by tier. See the Tier page for details or contact us if you’d like to discuss upgrades or partnerships.

​
Best practices before submitting

  • Double‑check that Manifest Settings required fields are complete and accurate.
  • Confirm you have exactly one Production version and that it’s the one you intend to submit.
  • Run a final pass for policy compliance.
  • Ensure your app is Active.
  • Review App Events, IAP definitions (if applicable), and other settings for accuracy.