Prompting the users to upgrade their mobile appIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Challenge:When a new binary with features and defect fixes is released on the Android Play Store, users who have disabled automatic updates (via Play Store settings) do not automatically receive the latest version. This can result in: Compatibility issues with backend upgrades, potentially preventing users from connecting to the latest backend instance. Difficulty ensuring that a large user base transitions to the latest version promptly without relying solely on direct communication. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } AllCause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Next button is disabled because a newer version of the app is not available in the same release track (e.g., Production).Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 2. Solution:Google Play Store provides a "Prompt Users to Update" option under Recovery Tools, allowing developers to display an in-app update prompt. This feature ensures that even users who have disabled automatic updates are notified and encouraged to update to the latest version, especially in critical scenarios such as: Backend changes that necessitate the latest client version for compatibility.Urgent defect fixes or security patches.New features that significantly enhance user experience or functionality. By utilizing this tool, developers can improve app update adoption rates and minimize compatibility issues caused by outdated versions. 3. Prompting Users on New Version Availability: The "Prompt User to Update" feature only works for the same release track. For example: If version 19.0.0 was released on a Closed Track, you can prompt users to update to version 19.1.0, provided it was also released on the same Closed Track.Similarly, if version 19.0.0 was released on Production, you can prompt users to update to version 19.1.0 on the same Production Track. Steps to Ensure the "Prompt User to Update" Works: Identify the previously released app version.Confirm that a newer version of the app has been released and is available in the same track. Steps to Identify the Previous Version Check Release History: Navigate to Test and Release → Release History.Select the build number and app version you want to target for the update prompt.Ensure a newer version of the app has been released, reviewed, and moved to Production. Use Recovery Tools to Prompt Users: Navigate to Test and Release → App Bundle Explorer.Search for the app using its build number.Select the build and click on "Prompt User" under the Recovery Tools dropdown. Initiate the Update Prompt: Specify the target audience for the pop-up.Click on "Initiate Pop-up." 4. Behavior of the Update Prompt: Once initiated, the update prompt behaves as follows: Persistent Notification:The pop-up appears every time the user opens the app until they update to the latest version.Dismissible Option:Users can dismiss the prompt by clicking the close button.Highlight New Features:The prompt displays a "What's New" section, summarizing the updates and fixes in the latest version.Seamless Update Process:Clicking on "Update" launches a full-screen update process.Once the update is installed, the app reopens automatically. 5. Testing Process: You can test the update prompt functionality without initiating it using a specific command. Refer to the below screenshot for the command syntax. Demo: This process ensures that users are notified about updates in a targeted and effective manner, improving the user experience and app engagement. If further assistance is required, please contact support. 6. FAQs: Q: What issue commonly causes users to miss updates?A: Users disabling automatic updates on the Play Store.Q: How can the issue be resolved?A: Use the "Prompt User to Update" feature to notify users directly.Q: Can the update prompt be tested before going live?A: Yes, via the command line in test tracks or Recovery Tools for controlled rollouts.Q: Why does the 'Prompt User to Update' option show 'No new version is available'?A: This occurs when there is no newer version available in the same release track. Ensure that the newer version is published in the same track (e.g., Production or Closed Track) as the current version. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Here is the google support doc: Prompt users to update to your latest app version