Forum Discussion
Solved
App Distribution Upload Issues: DevPost
Hi,
Posted this earlier in the general Forum and discovered this may be a better place for help.
I'm attempting to Upload a build to my Alpha Channel via the Meta Quest Developer Hub but it keeps failing.
Below is the Error message:
Error: An unexpected error occurred
{"cliErrorType":"UNEXPECTED_ERROR","cliErrorMessage":"File or directory 'D:\\**\\' was not included into executable at compilation stage. Please recompile adding it as asset or script."
I'm assuming this means I need to add the Directory and or filepath to the assets within my Unity Project but I'm not finding much in the way of how to actually do so. Please let me know if anyone has any ideas of how to do so or if you've encountered this error and found a solution.
Below is a screenshot of the error message.
The App is developed for PC and the build is for the Rift S. Once this is all good I plan on making a Quest Build as well.
Best regards,
assuming the build of your project is in z:\myprj\build\ and the exe is z:\myprj\build\launcher.exe below the command in full that (usually) works for me
ovr-platform-util upload-rift-build --app-id <yourappid> --app-secret <yourappsecret> --build-dir "z:\myprj\build\" --launch-file "z:\myprj\build\launcher.exe" --channel ALPHA --version "1.0"
7 Replies
I got the same problem many times ... to go straight to the solution (and it always works) ... You have to use something called "ovr-platform-util.exe", You can find it somewhere around on developer @ oculus ... open cmd (command prompt, best if You open it as administrator) ... then:
1) go to the drive\directory where You have the folder of You project
2) type a command like this
ovr-platform-util upload-rift-build --app-id <id of your app> --app-secret <app secret of your app> --build-dir <path-to-build-dir> --launch-file <path-to-launch-file> --channel LIVE --version <build-version>
3) just wait and boom, done
PS I wrote LIVE in the example, in Your case You should replace LIVE with ALPHA
Hi MAD-VF,
Thanks for the reply. I'll give that a try and let you know how it goes,
Best regards
Unfortunately I get the same error when using the CMD+OVR-Utility. I've attached the CMD Prompt, Powershell Prompt as well as the relevant Error from the Logs created. Still claims I need to include the file or directory at the compiler stage as either an asset or script. The error occurs just after beginning the upload and finding the files. Let me know if anyone has encountered this themselves. Thanks!
CMP PromptError LogPowershell Prompt
assuming the build of your project is in z:\myprj\build\ and the exe is z:\myprj\build\launcher.exe below the command in full that (usually) works for me
ovr-platform-util upload-rift-build --app-id <yourappid> --app-secret <yourappsecret> --build-dir "z:\myprj\build\" --launch-file "z:\myprj\build\launcher.exe" --channel ALPHA --version "1.0"
I might add couple of details here
Prerequisites :
Step 1 :Download OVR Util from here : Platform Command Line Utility
Step 2 : Place the .exe that downloads to a directory where you can/want to run command prompt(It is imperative that you run the command prompt interface where the ovr-platform-util.exe is downloaded/stored)
Step 3 : Follow MAD-VF 's solution, it is pretty self explanatory.
IMPORTANT Remove the "<" and ">" from the prompt when filling your own details in App ID and App secret
Thanks MAD-VF, that did the trick. Appreciate the help!
To resolve this issue, follow these steps:
Verify the size of the IPA. The maximum file size limit for all binaries is 2048 MiB, which is a little over 2 GB.
If the IPA size is within the file size limit and is reproducible, follow these steps:
Check your Info.plist file and confirm whether CFBundleDisplayName contains any <array> delimiters.
Note: App Distribution doesn't accept CFBundleDisplayName values that are arrays.
Remove the <array> delimiters and rebuild your app. The upload should succeed.
If you are still experiencing issues, contact Firebase Support.
If the IPA size is over the file size limit, make any necessary changes to decrease the file size.
If decreasing the IPA file size doesn't resolve the issue, contact Firebase Support and ask about using Testflight.Regards,
Rachel Gomez
