cancel
Showing results for 
Search instead for 
Did you mean: 

[RESOLVED] Uploading build to store fails with server errors

FableDev
Honored Guest

I've been trying to upload a final AAB file, built in Unity, for review for production.  I've tried using the "Meta Quest Developer Hub", then I tried the command line tool "ovr-platform-util".  In both cases, when attempting the upload there is a repeating "server error", and an eventual final error before the upload aborts.

Focusing on "ovr-platform-util", the console output repeats ""A server error occurred. The request will be retried.", starting every few seconds, then slowing down over time.  After this error is repeated 10 times, there is a final error of "ERROR: An unexpected error occurred" before the terminal command aborts.

The error suggests an issue on the meta server, but it's been doing this since yesterday morning, and it is now the afternoon, which seems like a long time for a server-side issue to remain unresolved.

FYI, the terminal command I ran, which produced this error, is below (with the app-secret redacted).  I recognize that I'm listing the AAB file under the "--apk" parameter, but there is no "--aab" option listed in the help in "ovr-platform-util", and trying "--aab" gives an immediate error of "Invalid parameter: 'aab'. Did you mean obb?  Missing required argument: apk".

./ovr-platform-util upload-quest-build --app-id 9467369169965906 --app-secret **** --channel LIVE --apk /m/_fablevision/cyark-resonant/Resonant_Mesa_Verde_VR/Build/resonant_250506.aab

 

1 ACCEPTED SOLUTION

Accepted Solutions

FableDev
Honored Guest

I've determined that the issue was in trying to use the AAB format instead of the APK format.  I've switched to the APK format and was able to get it uploaded.

I consider this issue resolved on my end, though I suggested to the support team that a more informative error message would be a good idea for issues of this nature.

View solution in original post

1 REPLY 1

FableDev
Honored Guest

I've determined that the issue was in trying to use the AAB format instead of the APK format.  I've switched to the APK format and was able to get it uploaded.

I consider this issue resolved on my end, though I suggested to the support team that a more informative error message would be a good idea for issues of this nature.