ovr upload fails due to missing android exported in manifest
I started receiving the following failures from ovr-platform-util when uploading quest apks with multiple apps and no changes to my manifest file: The AndroidManifest.xml contains an <intent-filter>, but android:exported was not set on its parent node. Add it to your manifest and try again. See https://developer.android.com/about/versions/12/behavior-changes-12#exported for more details. Anyone else experiencing this ?
Issue with ovr-platform-util
Hello, After the upgrade to 1.96.0.000001 the push of a new build is not working anymore. There is a generic error shown, here is a print screen, and the logs. :cross_mark: ERROR: An unexpected error occurred 2024-03-04T19:19:19.927Z [ERROR] Server log: {"app_id":6299260076841377,"client":"COMMAND_LINE","log_level":"ERROR","event_name":"UNEXPECTED_ERROR","stack_trace":"Error: ENOENT: no such file or directory, stat ''","extra":"{\"caught\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.96.0.000001\",\"compatibility_version\":2,\"session_id\":\"6299260076841377_2024-03-04T19:19:16.356Z\",\"command\":\"upload-quest-build\",\"app_id\":6299260076841377,\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.96.0.000001","session_id":"6299260076841377_2024-03-04T19:19:16.356Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":3571} 2024-03-04T19:19:20.126Z [ERROR] Server log: {"app_id":6299260076841377,"client":"COMMAND_LINE","log_level":"ERROR","event_name":"COMMAND_FAILED","stack_trace":"Error: ENOENT: no such file or directory, stat ''","extra":"{\"caught\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.96.0.000001\",\"compatibility_version\":2,\"session_id\":\"6299260076841377_2024-03-04T19:19:16.356Z\",\"command\":\"upload-quest-build\",\"app_id\":6299260076841377,\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.96.0.000001","session_id":"6299260076841377_2024-03-04T19:19:16.356Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":3770}
File 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
ovr-platform-util set-release-channel-build fails when targeting the default Production channel
We are using ovr-platform-util "set-release-channel-build" command in our release pipeline to push our latest builds to Oculus dashboard. We have no issue with our internal channels, but it's impossible to push to the default production channel of the app. We get the following error from ovr-platform-util: ERROR: The provided release channel (Production (App Lab)) does not exist. This channel was present by default when creating the app in Oculus dashboard, and we use it to release to our users so it's not possible to switch to a different one. Things we tried: - Creating a test channel with spaces and parenthesis in the name: the set-release-channel-build command works on the test channel - Deleting an unused internal channel called "Production" to avoid potential name conflicts: no changes - Calling the set-release-channel-build command using "Production" to see check if oculus use a different name internally for the default production channel: no changes We noticed that unlike all other channels in the dashboard, this one does not show a user count. All other channels have one, so there might be something to it, like the Oculus API not treating it as a regular channel? Would really appreciate some feedback from Meta/Oculus on this as it's impossible for us to have a functional release pipeline for our Quest app at the moment.
ERROR: Before uploading the build, please agree to the developer sales agreement from the following
When I create a new organization from https://developer.oculus.com/manage/organizations/create and upload an app using ovr-platform-util, I get an error message "ERROR: Before uploading the build, please agree to the developer sales agreement from the following" and the upload fails. I can't find the Developer Sales Agreement section in the legal documents of the development dashboard and agree to it. I also belong to another organizaition. I can find the Developer Sales Agreement section under another organization > Legal Documents and successfully upload the build. However, recently created organizations cannot find the Developer Sales Agreement section from their legal documents. The organization created this time was created after the introduction of the meta account, so is it possible that the items listed in the legal document have changed?Uploading apps via linux
Since the web upload is no longer possible could you provide the commandline utility for Linux? I did all my openXR dev with Android studio under Linux but then had to re-boot to Windows and then download the SDK again and compile it again. I don't mind working with a commandline tool which complements ADB under Liniux. Oh, and it would be great if that could also do screen capture as ADB at full landscape resolution.node:fs:585 Error uploading Quest build with Unity, ovr-platform-util, and ODH
This error occurs whenever I try to do an build upload. I've tried uploading from ODH, Unity and the ovr-platform-util. All generate the same error. I even just tried using ovr-platform-util with no arguments and also get the same error. For reference, - I don't have a D:/ drive (shouldn't matter) - The app was installed and run on my M:/ drive (SSD) Details below: node:fs:585 handleErrorFromBinding(ctx); ^ Error: UNKNOWN: unknown error, open 'D:\full-fbsource\arvr\js\node_modules\yargs\locales\en.json' at Object.openSync (node:fs:585:3) at Object.openSync (pkg/prelude/bootstrap.js:739:32) at Object.readFileSync (node:fs:453:35) at Object.readFileSync (pkg/prelude/bootstrap.js:1025:36) at o._readLocaleFile (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) at o.__ (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) at C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js at Object.<anonymous> (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) at C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js at a (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) { errno: -4094, syscall: 'open', code: 'UNKNOWN', path: 'D:\\full-fbsource\\arvr\\js\\node_modules\\yargs\\locales\\en.json' }How do you specify your app as Windows 10 only in ovr-platform-util ?
ovr-platform-util used to have a -w {"7SP1" | 8.1 | 10} option that let you designate your application as supporting Windows 7 and above, 8.1 and above, or 10 only. This is still in the documentation but appears to have been removed from the latest ovr-platform-util and generate an error if you specify it as a command line argument.
