Versions mismatch in Lifetime and Service Center

Does anyone experienced versions mismatch for native apps in Service Center and Lifetime? Environments are the same - UAT. Why do I need to tag and generate a new version in LIfetime? 

Thanks,

Roman

Hi Roman,

Is it the case, that an update was made and new packages have to be tagged and generated?

Id suggest to take a look here, to see the scenarios when is needed to tag again a mobile app:

https://success.outsystems.com/Documentation/10/Delivering_Mobile_Apps/Mobile_App_Update_Scenarios

Regards,

Yes, there was a plugin that was updated to the more recent version. However, I still don't see a reason for mismatched versions in lifetime and service center. 

Hi Roman,

Usually a tag of a mobile version is automatically updated, however some changes to the app don't generate a new mobile package, and a new snapshot of the app status, including mobile version package is needed.

I'd suggest this document also, where you can find more information:

https://success.outsystems.com/Documentation/10/Managing_the_Applications_Lifecycle/Deploy_Applications/Tag_a_Version

Regards,