Build stuck on "Malware Test" for days
Hi, We have uploaded a new build to the RC channel of one of our live apps, but it has been stuck on "Running Malware Review Test" since Friday. I have attached a screenshot below: I hoped this was just a visual bug but when trying to push it to the Production channel, this is not deploying live onto any headsets. I have seen online that this issue (being stuck in testing state) appears to occur randomly. Examples: https://forums.oculusvr.com/t5/Developer-Dashboard/Test-State-Stuck-On-Running-for-Store-Channal/td-p/727851 https://forums.oculusvr.com/t5/Developer-Dashboard/Uploaded-builds-can-t-get-past-quot-Running-quot/td-p/733675 https://forums.oculusvr.com/t5/Tool-Feedback/Stuck-at-uploading-build-Oculus-Developer-Hub/td-p/949230 Anyone experiencing this at the moment, or has any past experience to share? I have opened a support ticket with Meta but no answer yet. On that front, it seems the list of topic you can create support tickets for has been reduced and there isn't any "release/store support" field anymore, which makes it a bit convoluted, so any advice on this would be great as well. Thanks in advance!
My 10 year old son would like to publish his own developed game into the Meta Quest store
My son build his own VR game called Monkey Adventure and after weeks of building, testing, building and testing again with friends in private with APK builds he's ready to publish his game into the Meta Quest store and bring it to the public. After days of struggling filling the game, he get's stuck at the verification part. Is there a developer path designated for enthousiast kids he can take to make this happen, as he has no developer license (he's 10 years old) or business license at this point. If not, there should be in my humble opinion as these young folks are the future and are very talented and eager to learn at younger age. Thanks in advance!
Build Upload Failed
I am having a problem uploading the latest build for my game to the Alpha channel. I've found several similar posts, but in each of those there's at least some sort of error information. Here's what I get... Not a lot to go on there. In case it's something to do with the version numbering, I am attempting to update from build version "0.3asw.153" to "0.3b.160" --I tried rebuilding as version "0.4.160" but that fails exactly the same way. I'm reduced to shots in the dark with no error information at all. I'd be grateful for any suggestions how to resolve this issue.Best practice for supporting Quest vs Quest 2 vs Quest 3 differently?
With the gradual improvements in hardware, what is the best practice for submitting a game that supports different hardware capabilities? E.g., different Unreal Engine features are turned on for Quest 3 vs. Quest 2, requiring different build configurations, resulting in different cooked data for the builds (materials, etc.). It's the same app, but either a different apk or different data must load depending on the install hardware.
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!
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?
