Build generation for a pre-existing Play Store app

Overview

When you have an existing app already published on the Google Play Store or Apple App Store, Emergent can generate new builds that preserve your app's identity and signing credentials. This allows you to update your app through Emergent while maintaining continuity with your existing store listing.

To do this, you'll need to provide Emergent with the signing credentials from your original app. This page walks through extracting the required credential files for both Android and iOS.

Android signing

If you built your app on Emergent from the start, signing is fully handled for you: Emergent generates and holds the signing key and uses it for every build. Just click Publish, then Build, and submit the resulting

.aab

The exception is when you already have an app listed on the Play Store with the same package name, signed with its own key. The new AAB won't match the listing's signing key, so the upload fails with a keystore mismatch. To resolve it, contact support@emergent.sh - there are two ways, and support will help you pick:

• Align Emergent to your key: share your existing

  .jks

  file and keystore credentials, and Emergent updates the signing setup on our side.
• Align Google to Emergent's key: Emergent provides SHA fingerprints and a

  .pem

  file that you upload in the Google Play Console as an upload-key reset. The Google side typically takes 2-3 business days to process.

iOS: App Store Connect key

For iOS apps on the App Store, the App Store Connect API key is auto-created and Emergent-managed after your first TestFlight upload - you do not need to supply one yourself. There is no upload field for push keys in the build settings - if your app uses push notifications, ask the agent to set up Emergent-managed push notifications and share your credentials with it before building. If a build fails around push credentials, contact support.

.p8