Reuben Mark Mandap wrote:

Hi,

Go for any one of the below :)

Situations When the User Must Install a New Build

Even though every time a “1-Click Publish” runs the changes are automatically made available to the application, some changes require the end-users to install an updated application package on the device. It happens when:

• the configurations for a mobile platform were changed 
• the Extensibility Configurations property was changed, for instance, modification, addition or removal of mobile plugins, changes to status bar transparency, custom icons or splashscreens, and so on 
• an external resource of a plugin was updated
• the application name was changed 
• the entry module or its name was changed 
• the application icon was replaced 
• the main color of the application was changed 

Thanks

Hi Reuben,

These components may help.
https://www.outsystems.com/forge/component/3493/mobile-must-install/
https://www.outsystems.com/forge/component/2913/app-version-plugin/
https://www.outsystems.com/forge/component/1573/buildinfo-plugin/

I did the same functionality before in my project.

Basically, I put the latest version of my application in an Entity then, when a user tries to open the mobile application, compare the current version of the mobile application with the server version. If they aren't equal then create a message for the user then close the application.

I hope it helps.

Best Regards,
Ferhat