Changing package name
I loaded an package with the wrong name. If I try to load an new package with a new name, I get an error: com.OldComp.OldName ---> com.NewComp.NewName This upload uses a new package name, "com.NewComp.NewName", but the package name must not change between versions. Please upload a new build with the original package name, "com.OldComp.OldName". how i can change package name?
Build 'Malware Review Test Running' taking extremely long and keeps adding
Hi, I experience a problem with the 'Malware Review Test Running'. I'm working on my game and I've been uploading new builds. But the 'Malware Review Test' never finishes. It even adds a new test after a while. It's been so bad that 1 build that I've uploaded about 5 days ago still has tests running. To the point that I cannot even view the test status view of that build anymore because it gives an error saying: 'Please reduce the amount of data you're asking for, then retry your request' Is this a global problem? Or maybe a problem with my game specifically? I'm scheduling a release soon and this is blocking that at the moment. Thank you in advance!
My app already supports Go & Gear VR. Moving to Go only. What should users expect?
I'm not clear on what my Gear VR users should expect if I change my existing app to support only Go moving forward. We would do this because of upgrading the SDK suite / integration from version 1.41 or lower to 1.42 or higher within the Unity project. As Oculus no longer officially supports the platform, we need to follow suit at some point or be stuck with an old SDK for too long. This is okay, given our small population of Gear users. However, we'd like to let them know in advance what will happen, and I really don't know for certain from the information seen thus far. The official announcement only clarified perhaps the most obvious points (I can't post links yet, but it was November 7, 2019 "Gear VR App Development no Longer Supported From Oculus SDK Suite 1.42 and Future Versions"). The current build on our STORE channel is Gear compatible. At some point we would update with one produced with a newer SDK, which will not be Gear compatible (Go only). Has anyone else done this already? If so, what did your Gear users experience? If their last compatible build remained installed, could it still be restored if it got uninstalled at some point later? We are aware that a newer incompatible build is not supposed to appear in the Gear store. If another build channel were created to have all the Gear users as members, would it change the situation at all? Anything else noteworthy? We are looking for an official response as well, but it's good to have the answer clarified among the community.
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"