Forum Discussion
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!
12 Replies
Thank you for bringing this up on our forums page; we understand how time-consuming dealing with this issue can be. So, based on the information you provided, it appears that the ENOENT error indicates that you are missing a resource file. We would be delighted to assist you in reviewing the internal data of whatever app you appear to be attempting to upload. However, you might have better luck and learn more useful information in our Developer forums. You can get to them by clicking on this link.
Thank you, I will repost in the developer forum
Of course @islanduniverse.3D. It was a pleasure pointing you in the right direction to get assistance with your issue.
Were you able to fix this error? I am getting the network_error without the API_error and I haven't been able to find a solution for it. I would appreciate some help on this.
I was not able to find a fix for it. I searched for a general answer on what ECONNRESET means:
"Error: read ECONNRESET" typically means that the connection between the client and server was reset or closed unexpectedly. This can happen for a variety of reasons, such as a network issue, a problem with the server or application, or a timeout on the connection. The error message is typically generated when the client is trying to read data from the server and the connection is no longer active.
I tried making sure my VPN was off, that my connection was solid which it was. Nothing worked so it really made me think that its an issue on Meta's server side. The only way I was able to get around it was using the OVR Platform Utility tool to upload a build through the cmd window. Even then it had multiple server errors but it eventually uploaded after a long time. You could possibly try that and see if it works. The only other issue was that it took close to 24 hours to run the automated testing after that which again makes me think it might be caused by a Meta slowdown. I havent tried using Developer Hub since but will probably attempt it again later todayHey thanks for the reply. I tried using the OVR Platform Utility tool to upload a build through the cmd window and I was able to get through, however, I found other errors that i need to fix. At least now I know how to get around it!
One way to diagnose this is to upload the app bundle to the internal test track instead. While you'll get the same "Upload failed" error message, it may also give more information about the error
Example:
In this case, the error was due to having dist:onDemand attribute and <dist:delivery> settings at the same time.
Regards,
Rachel Gomez
Thank you for the reply. As a beginning developer im not sure what this means though. What is the internal test track? Is that something specific to Meta or is it just android related? When I google that I dont see anything pertaining to Meta and quest development specifically. what exactly is the dist:onDemand attribute and <dist:delivery> setting? Is that something related to my unity project settings? Do you have any links to relevant documentation so I can familiarize myself with these terms?
This error generally occurs due to the internet connection. It may be beneficial to try a different internet connection with better upload speed.
