Skip to content
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

Not managing to check out cloud-xr framework dependency #1

Open
infixlabs opened this issue Dec 16, 2024 · 3 comments
Open

Not managing to check out cloud-xr framework dependency #1

infixlabs opened this issue Dec 16, 2024 · 3 comments

Comments

@infixlabs
Copy link

This is on MacOS 15.2 / Xcode 16.2:

Showing Recent Messages
fatalError


cloudxr-framework

Fetching from https://github.com/NVIDIA/cloudxr-framework (cached)
Creating working copy
Checking out 1.0.0
Couldn’t check out revision ‘de30e50050ba1c8360e0df84663ed14c406ade2f’:
    fatal: reference is not a tree: de30e50050ba1c8360e0df84663ed14c406ade2f
Couldn’t check out revision ‘de30e50050ba1c8360e0df84663ed14c406ade2f’:



Resolving Package Graph Failed    12/16/24, 1:48 PM    1.6 seconds

Screenshot 2024-12-16 at 1 49 07 PM

Any ideas how to resolve this?

@matthias-nefzger-mw
Copy link

For me it worked to clone this repo: https://github.com/NVIDIA/cloudxr-framework
And then import the package dependency in XCode from the local clone.

You can also try to update the commit hash or branch in XCode under Project -> Package Dependencies.

@cauberthonda
Copy link

cauberthonda commented Dec 17, 2024

Turns out changing the Dependency Rule for CloudXRKit from "Exact Version" to "Up to Next Major Version" does the trick.

@arjundube-nv
Copy link
Collaborator

Thank you for raising this! We think there may be some caching happening which is causing the wrong commit ID to get used by Swift Package Manager. Changing the Dependency Rule is the easiest way to get Swift Package Manager to get to the correct version. I have also had success changing the rule to branch and specifying main:
image

We will add this to the known issues in our docs as well shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants