Uploading obb expansion files
When packaging games in UE4 (official release or Oculus version) and the game size is over 4gb, an additional expansion obb file is created called 'patch.[StoreVersion].[AppName].obb'. This corresponds with the official Android guidelines (https://developer.android.com/google/play/expansion-files). Sadly, we can't upload such files through the Oculus platform tools as it refuses the store version in the name. What is the intended way of handling this? Creating another activity just loading the file would work but would require some engine changes as well as changes in packaging workflow which are not needed or preferred for other standalone platforms. Thanks WouterFile Mapping for DLC-content with Ovr-platform-util
Hi! I have the following question: How do I specify the directory where DLC files go during the upload for the Rift Platform? This is the given expample in the docs: ./ovr-platform-util upload-add-on --app-id XXX --app-secret YYY --sku ZZZ --file <path-to-file> I need the file to go into the game's Paks folder (e.g. WindowsNoEditor\GameName\Content\Paks) When I upload a regular build (not DLC) I can specify a directory for all my game files, so the folder structure stays intact. But for the add-on upload process it seems I can only specify a file path. On Steam I can specify the file mapping for the content of DLC depots. How do I accomblish this for the Rift platform? Thank you, Marc
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?
Attempting to upload an app to the lab (focus aware manifest, min SDK version)
Hi everyone. I'm trying to upload my app to the Quest lab. The app is native (some JNI OpenXR and a Flutter android embedding for the UI). `ovr-platform-util` gives me two errors that I cannot seem to resolve: The Android min SDK version is 16, but should be 23 or greater. But, the min SDK version is set to 29 in every possible place I could find. The focus aware manifest meta-data tag must be set with required="true". There is <meta-data android:name="com.oculus.vr.focusaware" android:required="true" android:value="true"/> in the main manifest as well. How would I go about and resolve these errors? Many thanks!
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-... https://forums.oculusvr.com/t5/Developer-Dashboard/Uploaded-builds-can-t-get-past-quot-Running-quot/... https://forums.oculusvr.com/t5/Tool-Feedback/Stuck-at-uploading-build-Oculus-Developer-Hub/td-p/9492... 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!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-... https://forums.oculusvr.com/t5/Developer-Dashboard/Uploaded-builds-can-t-get-past-quot-Running-quot/... https://forums.oculusvr.com/t5/Tool-Feedback/Stuck-at-uploading-build-Oculus-Developer-Hub/td-p/9492... 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!
