Package from Git URL shows LFS Pointer file instead of actual content

Hello everyone, I have a problem with a custom package that we're working on for our customer. I've studied the documentation thoroughly but I cannot seem to find a solution.

Our setup consists of two Unity Projects that use Unity 2020.1.4f1:

Project A is the project that we work on the package in

<Unity project folder>/Packages/com.mycompanyname.something/

and is hosted on Github.

Project B expects this package in it's manifest.json

Code (json):

1. {
2.     "dependencies": {
3.             "com.mycompanyname.something": "https://github.com/mycompanyname/reponame.git?path=/Packages/com.mycompanyname.something"
4.     }
5. }

While we do not have any problems using Git LFS while pulling/pushing Project A, Project B loads the package but all files tracked with LFS just show the pointer files and not the actual files.

This suggests to me that Git LFS is not triggered by the way the package manager pulls packages from Github.

This command in bash tells me I have only one git-lfs.exe on my pc (/c/Program Files/Git LFS/git-lfs):

where git-lfs

This tells me that it is also using this exact file(/c/Program Files/Git LFS/git-lfs):

which git-lfs

This tells me that GIT_LFS_PATH=C:\Program Files\Git LFS is correct:

git-lfs env

I attached an extract from the Editor.log where it resolves the packages. Nothing interesting to see here.

Could this have something to do with administrative permissions or any other windows permissions in general?

I wonder, why is Project B unable to resolve the files tracked by lfs and instead loads the lfs pointer files?

 

Thank you for your quick reply! After upgrading to 2020.1.10f1 I get a different error. After a fixed duration of about 2 minutes of resolving packages, I automatically get this:



It seems to me that it now starts resolving via Git LFS but does not wait for it to be finished but instead after 2 minutes prompts this error (I have a slow internet connection).

Edit: It seems my problem is this: https://issuetracker.unity3d.com/is...-requires-exclusive-access-to-the-project-dot

 

I'm hitting this issue in 2020.3.14, and in the comments on that issue track you'll see someone with the issue in the latest LTS version as well, time of writing is 2020.3.16. I've tried enabling git lfs cache in upm user config file on macos, it's not changing the outcome. My files that are stoed in lfs are showing a few lines git lfs related text instead of their proper contents.

 

I had a similar error about corrupt PNGs from a package. I fixed it reinstalling git lfs:
brew install git-lfs

 

For anyone arriving here, the workaround (still) is to copy/move your .gitattributes to the same folder as package.json, as per: https://issuetracker.unity3d.com/is...ry-when-the-git-url-contains-a-path-extension

Confirmed in unity 2021.3.18f1 (latest as of today)

 

Hey! Yes, correct. Where should I send it?

Meanwhile, the particularities are:
- package's master branch is a normal Unity project with a "Assets/upm" folder, and a .gitattributes at the root
- on release, I use git subtree to create a vX.Y.Z-upm branch that only contains the "Assets/upm" directory's contents
- on the consumer side, the package is declared as

"com.<company>.<product>": "https://<token>@github.com/<user>/<repo>.git#v0.5.4-upm"

I have a feeling that just going over this list could give you a hint as to why it's not working, because it's an otherwise regular package, just some images and scripts

 

Nope, same repo. Reason is: have a branch with just that Assets/upm/* content at the root, to not need to add the path argument into the url.

But you make a very good point I oversaw.. with my setup, there won't be any .gitattributes in the resulted branch, since that subfolder's content replaces everything in the repo now.
Good point! Hope this helps others that are in the same situation

 

Faced the same problem, and same solution; copying .gitattributes into the root of the UPM package created by git subtree split fixed the issue with git lfs not fetching the lfs file contents. Thanks.

 

Sorry, not sure what happened when I tried to reply at the time, but yes, you're correct. Copying that file fixes it!

 

Hi !

I'm facing this issue right now. I add a package from a private GitHub repo and LFS files are not resolved, only the pointer is pulled.

I install the package with a specific branch, in the URL (ex :

https://github.com/MyOrg/MyRepo.git#develop

). The

.gitattributes

file is at the root of the package, in the same folder as the

package.json

file. And I have Git LFS installed on my PC (Windows 11).

None of the solution in this thread or in the documentation works ...