Build Deployment Automation Failing on Server Side using ovr-platform-tool.exe
Hi, I've been working on a bash script that deploys to the app lab using the ovr-platform-tool.exe, the idea is to hook it up in my build automation machine and for specific targets (like a release) deploy it automatically from Unity Cloud Build to the App Lab. I referenced a lot of the code provided in the Unity SDK, particularly the content of OVRPlatformTool.cs I'm getting a server side error: [error] ERROR: An unexpected error occurred [error] 2024-02-24T03:02:04.219Z [ERROR] Server log: {"app_id":6906526809465140,"client":"COMMAND_LINE","log_level":"ERROR","event_name":"UNEXPECTED_ERROR","stack_trace":"TypeError: Cannot read properties of undefined (reading 'eventStart')\n at y (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at Function.from (<anonymous>)\n at Object.genUploadChunksConcurrently (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js","extra":"{\"caught\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.96.0.000001\",\"compatibility_version\":2,\"session_id\":\"6906526809465140_2024-02-24T03:01:58.650Z\",\"command\":\"upload-quest-build\",\"app_id\":6906526809465140,\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.96.0.000001","session_id":"6906526809465140_2024-02-24T03:01:58.650Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":5569} [error] 2024-02-24T03:02:04.242Z [ERROR] Server log: {"app_id":6906526809465140,"client":"COMMAND_LINE","log_level":"ERROR","event_name":"COMMAND_FAILED","stack_trace":"TypeError: Cannot read properties of undefined (reading 'eventStart')\n at y (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at Function.from (<anonymous>)\n at Object.genUploadChunksConcurrently (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js","extra":"{\"caught\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.96.0.000001\",\"compatibility_version\":2,\"session_id\":\"6906526809465140_2024-02-24T03:01:58.650Z\",\"command\":\"upload-quest-build\",\"app_id\":6906526809465140,\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.96.0.000001","session_id":"6906526809465140_2024-02-24T03:01:58.650Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":5592} [error] [2024-02-24T03:02:05.869Z] - 7.3.35.2.7.4 - ERROR: User script exited with status 1. Aborting. [error] [2024-02-24T03:02:05.995Z] - 7.3.35.2.7.4 - ERROR: Build of 'release' failed. 783: unexpected token at '' Any idea about whether it's a bug or something I'm missing on my end? This is my current deployment script: https://gist.github.com/hector-yumebau/2611b0c094de90231ab1be461bf5e5e62.5KViews1like7CommentsRunning Unity PlayMode Tests on Quest
Hello there! I've been working on implementing PlayMode tests for my Quest app using the Unity Test Runner. I can successfully execute all the editor tests without any issues. However, I've hit a roadblock when attempting to run these tests on my physical Quest device, as I'm encountering some errors stemming from the entitlement check. Specifically, the error message I'm seeing is: "Unable to find AppId for package (com.UnityTestRunner.UnityTestRunner)." I've made several attempts to rectify this issue, including adjusting the properties of the APK build to use a valid package name that would hopefully resolve these errors. Regrettably, none of my attempts have been succesful so far. Has anyone managed to make something similar work?2.5KViews3likes2Comments
"Allow connected device to access files" blocking automation
I'm running into an issue working with Quest 2 headsets where the "Allow connected device to access files" pop up is now blocking us from running automation of our game on the headset. If I go to the device we use for automation and manually hit "Allow" on that prompt, the automation runs fine, but because we reboot the headset during automation runs, this is blocking us. Is there a way for me to: - Permanently allow this for a development machine? - Accept this dialog via adb / in some other automatable way?Solved1.5KViews1like1Comment