We are hoping to continue support for Quest 1 users while keeping that version of our app at sdk version 50. I've been looking around a while now for the best practice approach on how to potentially use release channels or something along these lines that isn't hacky and would continue to support these users with updates. One approach would be release channels, and ask Quest 1 users to manually switch release channels. Another solution would be to deliver builds to our release channel with different manifests, one that has <meta-dataandroid:name="com.oculus.supportedDevices"android:value="quest2|cambria"/>
and the older sdk. This would require some hacky versioning but seems like it could be more elegant for the user. Is there any solution that is being officially supported by Oculus in regards to allowing us ways to update and continue support for two parallel tracks like this ?
Follow up - saw this line in this post https://developer.oculus.com/blog/managing-meta-quest-1-guidance-developers/ "With today’s update, you now have more options for managing app support across Meta Quest devices via your app manifest. We have a solution coming to the Developer Dashboard in a few months, but we understand that some developers may want to freeze their Quest 1 builds earlier than that, so we're providing this short-term, manifest-based solution."
What will this upcoming solution be and is there more information on when we will have access to this?
We've been able to upload with "supportedDevices=quest2|questpro" to our release channel, that did not download to Quest 1. But the reverse did not work... A build uploaded with "supportedDevices=quest" also downloaded to Quest 2 & Pro, which was bad because those needed updates related to Android12 + firmware v57.
Hello, I am also looking for ways to support quest1, because this first generation quest saved the virtual reality industry when we were in despair, and we don’t want to give up on it.
