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.
App don't start after updating from AppLab
My app I am developing is not starting after an update until we restart the device. We are using Unity 2021.3 with addressables and spliting the app into apk and obb. Seems like the addressables are not correctly found after the update. It happened in incremental updates (few megabites) but also updates that downloads apparently the whole app again (1.1 GB). Then after restarting the headset it opens with no problems which makes me believe it is something wrong with the update process. Does anyone had this issue. Would be great to hear from the Meta team as well.
Store video updates don't work
I've been posting videos along with my app updates, but only see a thumbnail of them on the web Quest Store. They do play in the Meta Quest phone app, but the "audio toggle" does nothing so they're always silent. For instance Pro Feature Swap and More (oculus.com) Anyone else had this experience, or know a way to report this to Meta?
Quest 1 stuck on an old build
Hello, Recently I pushed v1.0.2 of my game (Home Detective) on App Lab, and when I browse to it on my Quest 2, I download that version, all hunky dory. However, when I download it using my Quest 1, I get an old build, v1.0.1. There is no prompt to update and it re-downloads that version even if I uninstall it and search for it again. Has Quest 1 already been deprecated from new builds, or is it something I have done? In v1.0.2, I did upgrade Unity and the Oculus SDK, but made sure I was still targeting Quest 1, 2 and Pro for the build. Thanks, David
Old user interface but on the most recent versions of Oculus software/runtime.
So in version 19 it became possible to test out the new "advanced" UI from the experimental features in the Settings. Sometime during a version 20 patch, it appears that it was no longer an optional feature, but instead became the new UI. I have had some of my users contact me and when they explain their UI, it is the old UI; Upon asking them to navigate to settings and get them to read me their version numbers, everything is the same as mine but they do not have the new UI. In fact, when they navigate to experimental features, they don't even have the experimental feature options to use the new UI. If anyone can assist me here, it would be very helpful.
Quest Build Stuttering + Peripherals Black after Oculus Update ( Unity )
Hello. I am using Unity 2019.3.15 to create a Quest build. I'm new to this. But I have meticulously followed all the suggested configurations and settings before proceeding with programming. After practicing on smaller stuff and after 3 full days of starting and then realizing I needed to start over, I got everything finally working smoothly. As I work, I test the build by staying connected to my PC via USB and via Link. Then sometimes I build to the headset just to double check everything. I was happy with my build and even tested basic functions on friends and family. Everything was working perfectly but then Oculus pushed an update through and then my next build became stutter/juddery. The field of view is also much smaller. The only changes I made in Unity were to the UI, the audio and to some capsule colliders for improvements so I don't know what could possibly be the problem. I was confused about the update because I'm almost certain that I already did an update a short time ago. One for desktop software, and maybe twice for my headset. Could it be that because I am building via Link connection that it's causing a problem with my Quest build? Please help, I was supposed to present today and now I'm stuck. More details about my scene... I have 2 video clips that play on awake in different locations of the scene embedded into screen models as textures. Basic terrain with a few trees painted with Poly brush. VERY minimal animated characters for atmosphere. I don't have a very good understanding of shaders and textures so I wonder if, I've used some incompatible asset or something.
