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!
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.
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?
