Publishing accounts and costs
Which Expo, Apple and Google accounts you need, what they cost, and how accounts differ from app records and signing.
You do not need every publishing account to start building. Choose where you want to test or release, then connect the accounts that route requires.
On this page
Choose accounts for your destination
| Destination | What to prepare |
|---|---|
Studio preview | Use Studio’s preview before setting up a store release. |
Android direct installation | Expo connection and project for the RNBlocks build path; an installable APK. A Play listing is not required for direct installation. |
iOS simulator on a Mac | Expo connection and project for the build path; Xcode with an iOS simulator. This build cannot be installed on an iPhone. |
Registered iPhone or iPad | Expo, Apple Developer membership, signing and the test device included in the provisioning profile. |
TestFlight or App Store | Expo, Apple Developer membership, an App Store Connect app record and store signing. |
Google Play testing or release | Expo build setup, a verified Google Play developer account, an app record and the relevant Play track. |
Example: Connections with the Expo form open. Account and token fields are empty.
- Open Connections in the publishing work area.
- Choose the provider, then follow its account setup instructions.
- Enter credentials only in the private form, never in the conversation.
Budget for separate services
These are separate accounts and bills. Buying RNBlocks credits does not pay developer enrollment or increase an Expo allowance. App sales, subscriptions and store commissions are separate from account enrollment.
| Service | Charge to plan for |
|---|---|
RNBlocks | Your plan and credits. Publishing-agent work uses RNBlocks credits; review usage in your account. |
Apple Developer Program | US$99 per membership year. Local prices vary by region; eligible organizations can apply for a fee waiver. |
Google Play developer registration | US$25 one time. Check the payment options and amount presented for your account. |
Expo | Build allowances and any additional usage depend on your Expo plan. |
Your app’s connected services | Provider API, database, storage and other runtime charges depend on the services your app uses. |
Account, project, app record and signing
A connected account is not the same as a linked app, completed signing, or a finished store submission. Check each result separately.
| Term | What it means |
|---|---|
Provider account | The person or organization with permission to manage resources. |
Expo project | The app’s project in Expo, used to associate its build work. |
Store app record | The listing and versions managed in App Store Connect or Play Console. |
App identifier | The iOS bundle identifier or Android package name identifying the installed app. |
Signing | Credentials and configuration that authorize an installable build for its destination. |
Use the account that owns the app
Saved Expo and Apple connections can be reused across RNBlocks apps. Each app still needs its own project or app binding. For an existing release, use the account and identifiers that already own the listing.
In Connections, Unlink from this app removes the current app’s binding. Disconnect account removes RNBlocks access for the linked apps shown in the confirmation. Provider projects and builds are not deleted by that action.