If an update is available, force the user to download and apply it, using Android's "Immediate" update strategy UI (the prompt can in fact still be dismissed). If this action is not triggered manually from a template, the update will be installed on the app's next init (e.g. Further details in Google's DocsĪfter a flexible update has finished downloading, this action will finish applying the update, by installing it and relaunching the app. If an update is available, prompt the user to download and apply it, using Android's "Flexible" update strategy UI, which encourages the user to update but gives the option to not do so. click | app_update: complete) to have the corresponding effect. The app_update template action can be triggered with one of the following arguments (e.g. Upon triggering, A check will be made to see whether a newer version of the app is available and, if it is, the user will be prompted to perform an update according to the corresponding strategy. Once enabled, the template actions detailed below can be used. For more information about deployment configurations, see the Deployments documentation. In-app updates must be opted into for a given deployment by setting the enabled property to true on the APP_UPDATES constant in the app config.
More details, and examples, can be found in the Android docs.
0 kommentar(er)
