ovr-platform-util reporting "A network error occurred. The request will be retried."
Heya, My teammates and I have been encountering an error when uploading our builds. The utility keeps spamming that: "A network error occurred. The request will be retried." It seems to be working in spite of these messages, albeit quite slowly. I see there are older posts with similar issue, but were seemingly resolved. Is anyone else having this problem? Thanks!
Store upload - "Platform abandonnned"
Hello, I'm trying to upload an apk to the store for the Quest but I'm always getting a message "Platform abandoned" (translated from French) : I tried to modify the manifest to get around that but no change in the signature seems to do the trick... Also, as an information in case of interest, my app is also referenced as for "mobile phone" but I don't know why it went this way (it is intended for the Quest), neither how to change that... Anyone knows what that means and what parameter I should change to get over that error ? Thanks for you help.
Platform Command Line Utility tool bug
I'm glad that there is now a CLI tool for uploading builds. However, it seems that the current CLI tool's parameter parsing is broken (at least the application launch parameter parsing). If the beginning of your launch parameter string overlaps with any of the CLI tool's parameters (e.g., --launchparams "-server 127.0.0.1" in which '-server 127.0.0.1' overlaps with the tool's '-s' parameter) the tool will incorrectly parse the app's launch parameter as the CLI tool's parameter. In the example case I just gave, it appears that it will improperly parse two values for the app secret token: your actual app secret and "erver 127.0.0.1" - which ends up completely breaking the upload process, all of which can be observed in the tool's log file. If your app's launchparams were instead "-playback" - it would improperly parse your launch params to be "layback" - the upload might succeed, but your application's launch parameters will be broken. For my case, this makes the CLI tool pretty much unusable for my app, as all of the command line parameters I need to specify start with either -s or -p. There are ways I could potentially address this on my end, but I'd rather not go through the contortions of dummy parameters or changing my app's command line parsing. Is anyone else having issues with the build upload tool? Is anybody using it?Mobile Build Upload Error & Infinite Loop
Hello, Web upload as well as ovr-platform-util.exe doesn't work anymore for us. It always get into infinite loop with steps 1/3 2/3 3/3 1/3 2/3 3/3... Please find log file attached. Logs are full of stack traces like: "stack_trace":"at [eval]:18:1658\nat a ([eval]:16:506)\nat [eval]:16:652\nat [eval]:16:450\nat Object._log ([eval]:18:1997)\nat [eval]:18:1046\nat a ([eval]:16:506)\nat [eval]:16:652" Command we use: ovr-platform-util.exe upload-mobile-build --app_id 1757522977679878 --app_secret %secret% --apk R8-Android-Shipping-armv7-es2.apk --channel "ALPHA" --notes "tralala"Can't upload update to App Labs - "APK Not Signed" - Its signed.
Game is in Unity 2018.03. Just uploaded a build fine on 3/29. Went to upload a build today and I get "APK not signed" error. I've done the exact same build process I normally do, and it appears to be signed just fine using the same key I always use. Anyone else having this problem?Can not upload build
I'm trying to upload a build but getting an error message, here it is below. Incorrect file format. Please select a file with one of the following types: application/zip, .zip The thing is, the folder is a .zip folder, and I have always used the same method for uploading builds. Not sure whats going on, I tried asking on the discord but no reply for the moment. I have had to delay this update, which is a bit annoying since it is an extremely important update and fixes game breaking bugs. Anyone know whats going on? I tried clearing cookies and doing all sorts of stuff. Tried restarts and making the build again. I even tried uploading a previous build that had been uploaded before but get the exact same error. Any idea on whats going on?
