"Multiple Devices Can't Access This App At The Same Time" Error for my App with Latest QuestFirmware
In-house Quest 2 headsets started getting this error ("Multiple Devices Can't Access This App at the Same Time") as soon as they got the new firmware today, whenever more than one person (logged into the same developer account on multiple Quests) launched the application at the same time. This hasn't been an issue for us in the past. I assume there's some permission flag we need to set to allow this, but I'm struggling to find it. Does anyone have any guidance? Thanks! -Eric
Developer Verification doesn't work - Two-step SMS issue
Hello, I'm trying to re-enable my developer mod on the latest build of quest 2, I've used developer mod since last year and for some reason, it has been disabled. When I looked into the website I figured I need to do a verification and since I don't own a credit card in my name for now I tried SMS verification but I get this error: This Page Isn't Available Right Now This may be because of a technical error that we are working to get fixed. This is the page I use for verification: developer.oculus.com/manage/verify/ Then when I try to enter the phone number i get the error page. I also tried adding two-step on my facebook account and connecting my oculus and facebook account, but it doesn't work.(I added T-S on facebook but it won't carry on to oculus, only now there is a third option added to developer.oculus.com/manage/verify/ that says: Add mobile number to Facebook, which i don't understand since I Did add number to facebook) I've been using developer mod for my university project for some time now and since I'm in a rush this is creating some turbulence in my work. I'm wondering if the error is going away anytime soon or if there is any other way to enable my developer mod. Also I did contact support team, but everyone says account verification isn't their thing ... it's an unwanted child.MQDH / Developer Dashboard - Server Error - API Error - No Tests Ran on Build
I am having a number of issues with Meta Quest Developer Hub and Developer Dashboard. For the past three days I have been unable to upload a build through MQDH due to a few different errors. I am using the latest version of MQDH. When uploading a build I either get an API_ERROR, ECONNRESET error, or PROCESSING_ERROR "please try again later". Looking at the logs it said server error, attempting to try again, and does this over and over. It doesnt seem to be an issue with my actual build, or manifest or anything that I am able to solve on my end. Have tried reinstalling MQDH or switching the adb file path to match unity. After repeated attempts failing through MQDH I decided to try using the OVR Platform Utility Tool. I was able to upload my .apk with an OBB file, though I received multiple server errors in the process. After about and hour and a half the upload process finally succeeded through the server errors and I am able to see my new build in developer dashboard inside a new release channel. My new issue is that the new build uploaded has not yet gone through the automated testing. I uploaded the build over 16 hours ago. Dashboard still says "No test runs were found to be associated with this build." Because of this I cant actually install and play this new build. And with both MQDH and Dashboard causing issues I am at a complete standstill on my project. Is there some sort of server issue on Metas side that is causing this? Any assistance is greatly appreciatted
Players reporting that my game is not available in their region even though...
Players from Russia reporting that my game is not available in their region even though it was previously available to them (they had purchased the game on AppLab). Not getting political. Those are just the players reporting the issue. Is anyone else experiencing anything like this?
Meta Quest 2 No longer working with my Vizio Quantum 4K TV.
We have 2 Oculust Quest 2 (Meta Quest 2) devices that streamed to our Vizio TV just fine until a few months ago. Then they both stopped. From what I can tell this was a conscious decision from Meta to stop supporting them. I purchased a Chrome cast device, but the shakiness was terrible. My TV is wired to a GB network. I wish Meta would fix this issue with Vizio TVs. I don't understand why the would stop support casting all of a sudden. This is rewally frustrating. I contacted Vizio and their support technicians had no clue. They said they just didn't support Oculus at this time. I've tried contacting Menta but not received a response. I just attempt to cast, the casting dialog appears on my Vizio TV and then the Quest 2 says there was an error casting to the TV. It works fine on multiple phones and computers in our house. All devices are on the same network. Very frustrating.Build error when using visual scripting ("Effect OculusSpatializerReflection could not be found")
I have a test project in Unity and until now it's worked fine. But now I get the following error when I try to build it: Error building Player: Effect OculusSpatializerReflection could not be found. Check that the project contains the correct native audio plugin libraries and that the importer settings are set up correctly. I don't know why this would be occurring as I didn't touch the spatializer or audio setup. All I did was add a visual script on the CenterEyeAnchor to set the background color based on the distance between two objects. (The two objects are controlled by the eye tracking, one on each eye; I'm doing it to see how well the distance works as a Z axis.) Previously I didn't have any visual scripts in this project (or any custom scripts at all) so maybe that has something to do with it. I tried removing the visual script and that didn't fix it, but I'm still seeing the thing saying it's building the visual scripts, so maybe clearing out whatever is causing that would fix it? Still though, I'd like to be able to use visual scripting because I find it a lot more pleasant than code for experimentation purposes. I tried Googling the error message, but the only result I found is from someone who was trying to play a game and running into an unrelated issue (related to it being a pirated copy) and a similar message happened to appear in the log file they posted.
