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.

'Immediate' update, which requires the user to update and restart the app to continue using it.

'Flexible' update, which provides an optional, background update process.

The UI presented to the user is handled by Google's Play Core service, which offers two different update flows:

a newer version of the app is available in the App Store, it is possible to alert users from within the app and prompt them to perform the update. When an update is available for the app, i.e.

- PR title descriptive (can be used in release notes).

Studio ready driver