Forum Discussion
Quest now unusable for developers and demos
I have an application that we are constantly modifying and before publishing the application to App Lab we sideload the APK for testing. This testing APK allows access to settings otherwise not available in our App Lab build. As of late the device is unusable: It incessantly updates itself to the latest App Lab build and this is a behavior we CANNOT SUPRESS.
Additionally, cloud backup sabotages our application, it is almost certain that after one of these cancerous, uncommanded software updates, that our app will be sabotaged by yet another unwanted feature.
1) HOW DO WE DISABLE THESE TERRORISTIC UPDATES? I have never seen something this toxic, even viruses are less persistent.
2) How can we build our app with a flag that specifically disables this cancerous cloud backup that constantly sabotages 100% of our installs?
We require this assistance ASAP as we are unable to test builds properly on our devices since these heinous, totalitarian and incompetent software update behaviors have been randomly implemented against everyone's will.
2 Replies
One solution is building with a different bundle ID from your AppLab release. It isn't at all optimal, but it is what we do to get around these issues.
It's a hack and in one case something I simply cannot do. There are many parts that depends on the bundle ID being intact, so changing it nukes half the functionality. We need manual control of software updates.
