Hii

Kindly check this OML

Hi Sunil,

The OML became huge so I will try to cut around and send you the relevant part. Anyway, let's start with the demo you sent. It might solve the whole issue. I will update here soon.  Thank you very much. 

Hi,

@Aurelio Junior is right in asking this question, but adding to his reply, there can be multiple reasons of change why you need to reinstall a new build of your app on your mobile device:

Even though every time a “1-Click Publish” runs the changes are automatically made available to the app, some changes require from the users to install an updated app 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 splash screens, and so on
• an external resource of a plugin was updated
• the app name was changed
• the entry module or its name was changed
• the app icon was replaced
• the main color of the app was changed

After these changes are published, the experience of the users with outdated apps may suffer some impact. In the case of plugins, it is a good practice to include fallbacks in the apps to avoid crashing until the last version is installed on the device. These potential issues are automatically fixed when the user upgrades to the latest app package.

The above is an abstract from the official documentation on this matter: 
https://success.outsystems.com/documentation/11/delivering_mobile_apps/mobile_app_update_scenarios/

Regards,

Daniel

I didn't know that I should do so. Wasn't written anywhere at the document. I will give this solution a chance and update you here.