Setup a native app
...
Preconditions for Test & Submi...
'Forced Update' for your App
Enable 'Forced Update' for your App
7min
purple manager summary this article will guide you through the steps to enable ' forced update forced update s s ' for your app so that you can prompt your users to update the app on their devices to the latest version made available by you in the google or apple app store in this example workflow, we create a forced update for ios and android at the same time please note, in case you only want to force the update for one of the platforms, you only select a new version of your app in steps 2 or 3 for the appropriate one preconditions have read this article about 'forced update' https //docs purplepublish com/setup/forced update for your app make sure that the app version with which you want to provide the 'forced update' is already available in the app store(s) and that the rollout was already completed please check in the app store (s) if your submitted app version is already available before proceeding with enabling the forced update have the links to your app store page(s) stored in purple manager (under 'apps' > 'basic settings' > 'select your target platforms for your apps') make sure to store the right app store url, otherwise, the user can't perform the update if you want to perform text changes to the 'dialogue' of your ' forced update forced update ' dialogue, this has to be done before submitting the app to the app store(s) learn more https //docs purplepublish com/setup/change the text of the screen dialogue for forced update you have the version of your submitted app built by hand how to 1\ go to purple manager > 'apps' > 'basic settings' 2\ next to 'select your target platforms for your app ', below 'ios' and 'forced update' select the version of the app, which you just have submitted to the apple app store, from the dropdown 3\ below 'android' and 'forced update' select the version of the app, which you just have submitted to the google play store, from the dropdown 4\ click on 'save'