When would you update an app instead of launching a new app?

  1. You have an existing app and you want to update it with a new app built with Fliplet

  2. You have an existing app produced with an old version of Fliplet and you want to replace it with an app built in a new version of Fliplet

  3. If you have created a new version of the app in Fliplet to replace the existing app

The benefit of updating an app instead of launching a new app:

  1. The user receives the new app automatically, they do not need to install a new app from the app store manually and delete the old app

  2. The app keeps its existing users

  3. You can still send notifications to the existing users

  4. You can keep the existing user data, if applicable

Get Started

  1. Steps to follow to update an app 
  2. Updating an existing app on Google Play

When updating an app, there are a few steps that must be followed:

  1. The app must be signed with the same Apple or Google account

  2. The app identifier/bundle must be the same

  3. The version number must be higher than the existing app

  4. After the new app goes live, all push tokens must be migrated from the existing Fliplet app to the new app

  5. Add the existing analytics software tracking tags, such as Google Analytics

1. The app must be signed with the same App Store or Google Play account

You can ensure you are submitting the app using the correct account by checking the developer account the current app came from

If you are updating your app with an app from Fliplet Studio version 1, please contact Fliplet to confirm your app’s details

If it is incorrect the app will appear as a new app on the app store

2. The app identifier/bundle must be the same

To confirm the identifier/bundle, access the existing app information, and check the bundle ID. It will be something like com.organisation.app-name For example, com.Fliplet.FlipletViewer

If you are using the latest version of Fliplet Studio you can find your Bundle ID here: Publish –> Publish to Apple devices –> App technical details –> Bundle ID

If you are updating your app with an app from Fliplet Studio version 1, please contact Fliplet to confirm your app’s details

If the identifier doesn’t match perfectly the device and app store will not know to update the existing app and the user will not receive the update

3. The version number must be higher than the existing app

If the version number is the same or lower the app store will not accept the app and the device will not install the update automatically as the device will think it already has the app

You can see the current version number by looking at the app’s details on your device or in the version information on the app store

4. After the new app goes live, all push tokens must be migrated from the existing Fliplet app to the new app

If you do not migrate user’s push tokens you will not be able to send them push notifications. To complete this step file a support ticket with Fliplet at support@fliplet.com and we can process this request for you

5. Add the existing analytics software tracking tags, such as Google Analytics

If you do not use the existing analytics settings, analytics data will not be tracked or it will appear in a new analytics account meaning you cannot assess historic usage data for your app before the upgrade

If you have any questions about replacing your app, contact Fliplet and we can advise you on the steps you need to take and how to take them

Updating an existing app on Google Play, that was not initially published through Fliplet

Should you want to replace an existing app on Google Play that wasn’t initially published through Fliplet, you might need some enhancements from Fliplet before being able to do so. This is because apps uploaded to Google Play are signed with keys

  1. Once the app is submitted to Google Play, all subsequent submissions to Google must be signed using the same app signing key. This will be a .jks file
  2. If you don’t have access to that key, you will need to contact the Google Play support team to reset the key
  3. If you do have access to the original key, we would require the Keystore file, Keystore alias, and Keystore password for the Google Play submission actioned outside of Fliplet
  4. This is then added to our AAB build configuration files for Android for your build
  5. Following this, you can then go ahead and submit the build via Fliplet Studio

Related Articles

Was this article helpful?
YesNo