The AppManager Livesync updates are connected to an app and a version. The best solution to your problem would be to have three different apps in the Telerik AppManager store - one for each environment. Apps are differentiated through their Application Identifier (you can find it in the Properties section of your project). Here is an example workflow:
1. During development you work on an app with an app id like 'com.domain.yourapp.dev'. It's best to change the name to 'Your App Dev', for example. You publish it to Telerik AppManager and distribute it as your dev environment test. You can then publish AppManager Livesync updates.
2. Once you think this is ready for QA testing, change the app id to 'com.domain.yourapp.test' and have the name as 'Your App Test'. Publish it to Telerik AppManager - it will appear as a new app there. You can then distribute this app to your QAs and publish Livesync updates to it.
3. Once the QAs have tested this, you can build and publish the app with the final app id and version, 'com.domain.yourapp'.
Note, that Livesync updates will be published with regards to the app id and version at the time of publishing. This means that you can change the app id back to 'com.domain.yourapp.dev', set the appropriate version and publish Livesync updates to the dev version again.
Also, this workflow works best with a version control service like Git, so that you can get back to the code on your Test environment easily.
Let me know if you have any questions.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items