Wrong package updated on phone application

Escenario: The QA mobile app is installed on your phone. When deploying development to QA, the app is refreshed and the productive app settings appear.

This application has a server function that allows us to know what functionality is available in the app dynamically. One requirement of the application is that in the way of "toggles", the client can turn functionality on and off in the application. To meet the requirement, we decided to create site properties (managed in Service Center and by environment) and when the application starts, you see what functionality is turned on/off. 

Other functionality are firebase logs and we can identify that the package update was done by certain logs that have not been updated. We have not made a new release to Production.

What is currently happening is that having the QA application installed on phone and deploying Development to QA, production configurations as well as un firebase logs appear on app

Another fact is that by reviewing the package generation settings (APK and IPA), I realized that in all three environments, the app has exactly the same application identifier

Could this be causing that the installation in the phone takes the wrong package? 

  • The Development version was generated with the certificate.
  • The QA version is uploaded to Testflight so that it can be tested.
  • The Prod version is in both stores (Play Store and App Store).

Three environments: Development, QA and Production

An end user has already reported the wrong behavior and our QA team is currently experiencing this mistake.

Hi Jennifer,

Didn't get your question completely, but here's something that you should make sure :

- Outsystems Mobile App performs seamless upgrades; So the moment you deploy from dev-->qa the app get's update.

 Incase the update requires attention then it has to go with an build update i.e what we rollout a build with new version.

Ref for more details:


- Coming to the App-Identifier; It's our call to keep whatsoever we can. But I'll suggest you to have diff package-name/identifier for each env. This makes easy when we have integrations with third-party services like firebase. Where we create a profile for each app mentioning the package-name.

Hope it helps,


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.