Developer Hub - Build Upload Failed - PROCESSING ERROR, API ERROR, ECONNRESET
I am trying to upload a new build of my game through the Meta Quest Developer Hub. I am uploading it to a private release channel for alpha testing. I am getting a number of errors after multiple attempts with a different error each time. I get upload failed errors sometimes showing Processing Error please try again later, API error, or ECONNRESET Network error. I've tried looking at the log files but Im not experienced enough to know what to do. It is strange because I havent had these issues before, I've uploaded multiple builds with the most recent being a little over a week ago. I am using unity 2021, the most recent version of MQDH, and am attempting to upload an apk and single OBB file (2.2 GB). I have tried copying the adb files associated with my unity project and pasting them into the "Meta Quest Developer\resources\bin" file path. I've also tried changing the MQDH ADB file path to match the unity version in the file path "C:\Program Files\Unity\Hub\Editor\2021.3.15f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools" Nothing seems to work and its more strange that different errors pop up instead of a single consistent error. I've made sure my manifest file is correct and am increasing the version and bundle code with each build, and done other things like make sure MQDH is able to pass through my firewall, tried making a fresh release channel. I also sometimes receive this error when attempting to open MQDH and I have to uninstall it and reinstall just to get it to reopen. Am i doing something completely wrong? Here are two of the errors, with the other one saying PROCESSING_ERROR please try again later. I can send log files if needed. Thank you for any help in advance!8.4KViews2likes12CommentsNew oculus Update make the controllers not work in UE5
After the recent Oculus Update, my controllers have stopped working in Unreal Engine 5. whenever I try to play in the editor or a working project build, the controls do not move or allow for input. They were working perfectly before the update. This is affecting the Oculus Rift CV1 and the Quest 2. From what I've read in the forum so far all Oculus headsets are affected and Facebook/meta are sitting on their hands doing nothing Both controllers are fixed to 0.0.0. in the world space and won't move or allow for inputs Two and a half years of work are now dead in the water until it's fixed. I have tried uninstalling and reinstalling the Meta desktop app. I have tried different solid builds that I know work. "Have you removed any third-party accessories that may affect power, battery fit, or controller detection. For example, rechargeable grips, controller covers, etc." - Yes "in your other attempts, did you unpair and repair the controllers to the headset?" - Yes "Have you checked the controller battery and the LED status (blinking, solid, or no light at all)?" - Yes I have a custom build development PC that can more or less handle anything so that isn't a problem.3.6KViews2likes7CommentsAge user group testing
Hi, I'm a Unity dev trying to update our games to work with the new age requirements from Meta. We have been setting up everything needed however we are not sure how we can test build the same way as a child (10-13 year-old) to make sure everything works as expected. Is there a way to change the age of an account to test the functionality?3.1KViews1like2CommentsSERIOUS ISSUE Quest Pro not Casting and I'VE DONE EVERYTHING!!
Please don't skip this isn't your run of the mill I can't get this going post. I have been working in and using the developer hub for along time and I CAN NOT GET AN ANSWER FOR THIS ISSUE! Long story short I can not cast through the Quest Pro on MQDH. When I try to cast I get the same error listed below. This used to work fine, it also worked on my laptop, now it works on neither. Also when I try to record it says the "display is off ...it's not. A few others have reported this issue with NO RESOLVE. I've tried everything, factory reset headset, factory reset PC, everything is updated, tried rolled back version of MQDH ETC and still not dice. It works fine with my Quest 2, I can also cast with the Quest Pro through sidequest AND the oculus casting website no problem but you can not record quality mixed reality content so they are worthless. This is only an issue with the MQDH and only with my Quest Pro. I'm not sure if it is the root cause but "allow usb debugging" does not pop up when I plug the pro in but it does when I plug the Quest 2 . I've been at this for weeks with no help! Everything is correct, developer mode, my developer mode account. I've tried turning developer mode on in of while the app while in the headset. I've tried different cables, different pc, even different operating systems and it STILL it refuses to work and it used to. I've toggle usb displays and developer options in the headset etc. Once again I'm not sure if this is the cause but it's the only thing different between the Quest 2 and Quest Pro when trying to cast. The worst part is it used to work, I didn't touch the headset for a month and now this.2.9KViews2likes8CommentsCant press upload on developer hub
So, my game has been inactive of updates for a while for the reason of I can't seem to upload a build without some kind of error and when I fix it I get a new one. Now I try to upload a build again but to my surprise I cant press the upload button. The button is completely gray as if I'm not allowed to press it so if anyone knows a solution to this please tell me.2.5KViews0likes3CommentsOculus Quest 2 Runtime Not Working/Switching to OpenXR
I'm stumped. I checked the Meta website to see if anyone has had a similar problem--and/or solved it. Sure, people have had their issues solved, but not me. As of now, I've updated my drivers (both headset and laptop), and restarted and updated everything I could think of. I also went through the SteamVR route, which didn't help either. I checked the developer portion of SteamVR settings and still couldn't switch it the runtime correctly. I went over to device manager, and made sure the USB ports were turned on and all that, weird things that Meta themselves suggested to another plea for help. Additionally, I installed the OpenXR toolkit off of the Microsoft webstore. Nothing much there... I'm going through all this because I just wanted to solve my Pavlov screen jitter issues--now I'm in a world full of problems 😕 Any help would be appreciated, please let me know!1.9KViews3likes2CommentsQuestion about Spatial Anchor saving
Hello Everyone, I am currently trying to work with shared spatial anchors, and what i wanted to do is basically understand, when i save a spatial anchor by saving it's Uuid, what information am i actually storing? If i were to provide another device with that same Uuid, what would happen? Would it be able to restore the anchor to its position in the real world? And if not, would there be any data i can share to make that happen? All in all, my objective is to save the position of an anchor (locally if possible) on one device, then restore it on another device when it installs the app (provided the scene is the same OR the scene anchor it creates is similar (not sure that's an option). Thanks in advance to any repliers!1.9KViews0likes3CommentsHelp, can't pass verification and get "successful" after "Verify Entitlement" blueprint
Help, can't pass verification and get "successful" after "Verify Entitlement" node . I add these lines to the "DefaultEngine.ini" file: [OnlineSubsystem] DefaultPlatformService=Oculus bHasVoiceEnable=true [OnlineSubsystemOculus] bEnabled=true OculusAppId=[my app id] When I tested this earlier, half a year ago, it worked, but now no matter what I do I can't get success. What changed? What am I doing wrong? I created a new app in appLab and took the App ID from there. But I didn't upload the app itself to the server.1.7KViews1like4Comments