Publishing to the App Store and Google Play

Open your App → Deploy, then choose Publish to App Store or Publish to Google Play. Appfully builds the store file for you: no Expo, GitHub or Mac needed. Each store is separate, with its own version.

What you need

Each build also uses Appfully credits: 15 for Google Play and 30 for the App Store. If a build fails, its credits are refunded automatically.

Google Play

1. Check the bundle ID (it can't change after your first release) and the version, then press Build .aab.
2. In about 15–30 minutes the build is Ready. Press .aab to download it, then upload it in Play Console.
3. Optional: add a Google service account key and Appfully uploads each build to the Internal testing track for you. Google requires the very first upload to be done by hand.

App Store

Apple only accepts apps signed with your developer account, so the App Store needs an App Store Connect API key (once):

1. In App Store Connect, create the app and note its Apple ID (a number).
2. Under Users and Access → Integrations, create an API key. Enter its Key ID, Issuer ID and the .p8 file, plus your Team ID from your Apple Developer membership page.
3. Press Build and send to TestFlight. When it's ready, it appears in TestFlight. Add screenshots, a description and a privacy policy there, then submit for Apple's review.

Your keys are stored encrypted and used only for your builds. Use Replace to change them.

Good to know

• Icon: the stores need a 1024×1024 app icon before review.
• New versions: change the version and build again. Build numbers go up automatically.
• Existing store apps: use the same bundle ID. For Android apps first published elsewhere, Google needs the original signing key or an upload-key reset in Play Console.