not updating

3 Topics

Pro controllers refuse to update after V79 update on headset
I've run loops with the support team with no help so thought I would come to the forums I have a quest 2 and I have the meta pro controllers after the recent software update they've refused to update I've tried resetting them unpairing and repairing charging them and when nothing worked I contacted meta support which the guy told to me factory reset and guess what it didn't work so now I'm stuck with a factory reset headset that I can't start the set up on because I don't got working controllers because they still say they need to update I don't know how to fix it I don't got a computer that I can use and I don't have another headset that I can pair the controllers to is there anyway to fix this? since Meta support did not help at all
gabbytheteaVR
9 months ago Place Other Troubleshooting
85Views
0likes
2Comments
.apk works when sideloading, but can't be uploaded to Applab
Hey there, I have a game on AppLab built with Unity that was initially released about a year ago. Recently I've been trying to upload an update with minor fixes using MQDH but all I get is an "Upload Failed" message with the text "The build you were trying to upload has failed. Build Upload Error - an error has occured for app id: 4879[...]". I CAN just sideload the apk via the "Device Manager" tab of MQDH and everything works fine on my Quest 2, which makes me think that the apk itself is okay. Plus, the error is exactly the same when I disconnect from the internet before trying the upload, so my guess is that the apk fails some internal check *before* it is sent to the server, but unfortunately, the error message is not very informative as to where the problem is located. I only remember changing the Minimum API level and the Build Name and Build Code in Unity, everything else is pretty much the same as with the version I uploaded a year ago without problems. I have tried multiple builds with minor changes and have tried uploading with different MQDH versions over a period of several weeks. Does anybody know this problem? Is there a way to contact a Meta engineer and have them take a look at the apk? Are there any known workarounds? How would you narrow down the error? Very thankful for any help and suggestions! Cheers, Felix PS: I posted this issue before in the Tools Feedback Forum, but I think this here is a more appropriate place.
Solved
Krakentanz
1 year ago Place Unity Development
2KViews
0likes
3Comments
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
TheDaddis
2 years ago Place Quest Development
974Views
0likes
1Comment