App Store & Play

Order of operations

1. Polish and Publish web.
2. Complete the Release passport, Bundle ID, and Apple/Expo credentials under Release.
3. Queue App Store (.ipa) and/or Play Store (.aab) builds.
4. Wait for a real production build to reach Success.
5. Ask the Build agent to submit the successful build. iOS needs the numeric App Store Connect app ID; Android needs a Google Play service-account JSON key. Appify requests either missing value through an encrypted field.
6. Approve the exact store upload. Google Play defaults to the internal track and draft status unless you explicitly request a wider rollout.
7. Use the exported release packet while completing screenshots, privacy/data safety, and age rating in each store console.

Accounts you need

• Apple Developer Program (for iOS App Store)
• Google Play Console (for Play)
• Paid Appify plan with native builds enabled
• A real EAS production build; simulated artifacts cannot be submitted

What Appify submits

For iOS, Appify queues the binary for App Store Connect/TestFlight. Apple review and public release still happen in App Store Connect. For Android, Appify uploads to the Google Play track and release status named on the approval card. Store processing and review can still follow.