Set up Apple publishing
Prepare Apple membership, an App Store Connect API key, the app record and signing for iPhone testing or an App Store release.
Apple setup has separate parts: membership, RNBlocks access, your app record and signing. A renewed membership or connected key does not finish every part.
On this page
Choose individual or organization enrollment
Individual enrollment uses your personal legal name as the App Store seller. Organization enrollment uses the legal entity’s name and requires an authorized representative, organization website and usually a D-U-N-S number.
Enter your legal identity in personal identity fields; do not substitute a brand name. Have the account holder complete verification, agreements and payment on Apple’s site. Membership is US$99 per year, with regional pricing and eligible fee waivers.
Already enrolled or working on another app?
Sign in with the existing Apple Account and choose the team that owns the app. One membership can hold multiple apps; each app needs its own bundle identifier and store record.
If membership expired, renew the existing membership. Check the account’s status and outstanding agreements afterward. Renewal does not register a device, create a profile or link an app record in RNBlocks.
Create or locate the API key
Open Apple’s key page
In RNBlocks Connections, choose Connect Apple → Open App Store Connect keys. In Apple, go to Users and Access → Integrations → App Store Connect API.
Choose the appropriate key
For iPhone signing, use a Team key. An Account Holder or Admin can create it. Select the role needed for the release; a team key can cover every app in that Apple team.
Download the private file
For a new key, choose Download API Key and confirm the download. Save the .p8 securely. Record its Key ID and the team’s Issuer ID.
Connect privately in RNBlocks
An Individual key can inherit your app access, but cannot set up iPhone signing. Use a Team key for that work. Sign in with Apple for a consumer app is a different feature from publishing access.
Fill the private form
Set Connection name and Key type. For a Team key, enter Issuer ID and Key ID, then select Private key (.p8). Keep the file out of the conversation.
Check the connection
Choose Check and connect. Review the result. Read access to apps or signing records does not prove permission for every later write.
Choose it for this app
Under Apple connection for this app, select the account and check the bundle identifier. Choose Use for this app. Look for the linked App Store Connect app record, or a message that none was found.
The actual RNBlocks Apple connection form. Secret fields and file upload are empty.
- Give the saved connection a recognizable name and choose the correct key type.
- For a team key, enter its Issuer ID and Key ID, then choose the matching .p8 file. Keep these out of the conversation.
- Check and connect verifies access. It does not create signing keys, start a build or submit your app.
Create the store app record
Open the intended team
In App Store Connect, open Apps → + → New App. For an update, open the existing app instead.
Match the app identity
Choose iOS, app name and primary language. Select the bundle ID saved in RNBlocks Release settings. If it is missing, register it under the correct Apple team first.
Create and link the record
Enter a unique internal SKU, set user access and create the record. Return to RNBlocks Connections and choose Use for this app again to check the matching App Store Connect record.
Apple’s official Backyard Birds example. It selects several platforms; select iOS for your iOS release.
Apple: Add a new app- Choose the platform for this release and the app’s name and primary language.
- Select the bundle identifier that matches your app, then provide your own SKU.
- Check team access before creating the record. The example values belong to Apple’s sample app.
Prepare signing for the destination
Ask the agent to check the signing setup for the selected app and destination. Review any proposed certificate or profile creation before approval.
For direct iPhone installation, register the intended device and ensure the profile includes it. A registration link completed on the phone is one step; the profile still needs to be prepared for that device.
A TestFlight/App Store build uses store signing instead of a registered-device profile. Choose that destination before preparing the build. An iOS simulator build is a separate artifact and cannot be installed on a phone.
Before you continue
If Apple asks for a new agreement or account verification, complete it in your own account and ask the agent to check again. Creating another API key is not the fix for every account problem.
The correct Apple connection is selected for the current bundle identifier.
The store app record is linked when the destination needs one.
Signing checks refer to this team, app and destination.
For a physical-device build, the intended phone is included.
Any interrupted signing or upload attempt has been checked before retrying.