# Publish your app > Move from Studio to a tested app, store screenshots and a reviewed release. Understand what happens in RNBlocks and in each store. Canonical: https://www.rnblocks.dev/docs/publishing Updated: 2026-10-01 Open your app in Studio and choose Publish. Your publishing workspace keeps the conversation, release settings, store copy, screenshots and build results together. Start with your next goal: test on a phone, invite testers, or prepare a store release. You can ask the agent for help at any point. ## Before you start - A saved app that you can open and use in Studio. - A decision about iOS, Android, or both, and whether this is a new app or an update. - Access to the relevant provider accounts when you reach account setup. ## Find your way around Section: https://www.rnblocks.dev/docs/publishing#workspace The plan tracks the release journey. The Publishing agent is your conversation. The work area contains Overview, Store details, Release settings, Screenshots and Connections when available. On a phone, switch between Plan, Conversation and Work. Open Work to edit details or inspect results, then return to Conversation to continue. ### Figure: Continue in the publishing workspace Wandr’s Publish workspace. Desktop shows Your release plan on the left, Publishing agent in the center, and a work area on the right with Overview, Store details, Release settings, Screenshots and Connections. On mobile, Plan, Conversation and Work select one panel at a time. 1. Use the plan to see the release stages. 2. Ask the publishing agent what to do next, or choose a starter prompt. 3. Open Work to inspect store details, screenshots, release settings and connections. Example: Wandr in the publishing workspace. Illustrated walkthrough. ## From your app to a release Section: https://www.rnblocks.dev/docs/publishing#journey 1. **Choose your release** — Tell the agent which platform you want and what to do next. For example: Help me test this app on my iPhone before preparing its App Store release. 2. **Prepare the app** — Ask for app checks. Set the app identity, connect the required accounts, write the listing and prepare screenshots of working screens. Resolve blockers before building. 3. **Build and test** — Choose a direct device build or a store testing track. Review the proposed build, install the finished result and test the main journeys. A successful build alone does not confirm that those journeys work. 4. **Review and submit** — Check the exact build, listing, assets and declarations. Complete the store’s review submission and choose how the app will be released after approval. - [Choose a testing route](https://www.rnblocks.dev/docs/publishing/testing) - [Submission and review](https://www.rnblocks.dev/docs/publishing/submit-and-review) ## What you need for a store release Section: https://www.rnblocks.dev/docs/publishing#checklist - Developer account: the right owner, completed verification and required agreements. - App identity: a stable iOS bundle identifier or Android package name, with matching signing setup. - Working build: test sign-in, navigation, permissions, connected features and failure states. - Store materials: app icon, name, description, screenshots and accurate release notes. - Public information: support and privacy pages, required data disclosures, and account deletion when applicable. - Review access: a usable review account or instructions when the app requires sign-in, plus any app-specific declarations. - [Accounts and costs](https://www.rnblocks.dev/docs/publishing/accounts) - [Websites and verification](https://www.rnblocks.dev/docs/publishing/websites-and-verification) - [Store assets](https://www.rnblocks.dev/docs/publishing/store-assets) - [Privacy and support](https://www.rnblocks.dev/docs/publishing/privacy-and-support) ## Know what has actually happened Section: https://www.rnblocks.dev/docs/publishing#control Saving Store details keeps a draft in RNBlocks. A reviewed provider action is a separate step. Read the result for confirmation of what changed, where it changed, and which app it affected. Available actions depend on your connections and release destination. RNBlocks supports Google Play draft uploads, initial listings, assets and Data safety. Account setup and some declarations still need Play Console; check the Google Play guide for the current capability split. A finished iOS upload can make a build available in App Store Connect after processing. It does not by itself submit the app for public review or publish it. > **Private account steps stay with you** > Complete passwords, verification codes, identity documents, agreements and payments directly with the provider. Use the dedicated Connections forms for supported credentials, not the conversation. - [Browser help and control](https://www.rnblocks.dev/docs/browser-control) ## Continue after an interruption Section: https://www.rnblocks.dev/docs/publishing#resume Reopen the same app’s Publish workspace and ask the agent to check the latest saved build or upload. Confirm an uncertain outcome before starting another attempt. If you changed the app or release settings after a review was prepared, ask for a fresh review so it matches the version you intend to release. ## Continue - [Build your first app](https://www.rnblocks.dev/docs/first-app) - [Release settings](https://www.rnblocks.dev/docs/publishing/release-settings) - [Update a published app](https://www.rnblocks.dev/docs/publishing/updates) ## Official references - [Submit an app to App Review](https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-app) - [Publish your app on Google Play](https://support.google.com/googleplay/android-developer/answer/9859751?hl=en)