-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Path does not exist error when running repo package #10
Comments
Thank you for this question and for following up with a viable workaround. Windows long path issues are known, and in the short term, we have added information about this to the relevant packaging documentation and tutorials. We will work to resolve this in a more permanent way in future releases via proper long path support for Windows. This question will remain open until resolved. |
I'm having the same issue, only with a different path - Tried moving the file to the primary drive folder, and running build and package from |
Update: this may be due to the |
When running
repo package
I get the errorPath does not exist
pointing to a script inside the extension omni.ui when I go to check if it exists it did. So I remembered that Windows doesn't like long paths and decided to clone the same repo in C:\ instead of the longer directory I was using inside My Documents.So I ran
.\build
and.\repo package
again but this time I used CMD instead of PowerShell (I don't know if this has anything to do with it getting solved) and this time I didn't get the error and the packaging process finished successfully.Source Code here, comparison with this repo's main. I just created and extension and added it to repo.toml to repo_precache_exts section.
This happened in 2 different computers before I did the workaround described above (I used to have the project in
C:\Users\User\Documents\Omniverse\Apps\my-kit-app
).EDIT: Confirmed using CMD was just placebo. It works with PowerShell too, the issue is just the same old windows issue with long paths.
The text was updated successfully, but these errors were encountered: