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
Update issue in 4.0.0 #1830
Comments
@Kedar-27, what version of cocoapods are you using? you can check with |
1.11.3 |
I'm not able to reproduce this issue on my end. Could you share a sample project and command that demonstrates this issue? Another question: what version of git are you using? you can check with |
git version 2.37.1 (Apple Git-137.1) |
Does the issue go away if you install Git LFS by running We started using Git LFS recently. My understanding is that this is supposed to be optional (you can still clone the repo without this installed), but it may cause issues in certain circumstances. |
Yes this worked. Thanks. Checked with both pods and via spm |
But why is it necessary to install Git LFS manually to migrate to Lottie 4.0? That's not a good approach. |
This is not intentional -- my understanding was that it shouldn't be necessary for consumers to install Git LFS to clone the Lottie repo. e.g. If a lot of consumers are encountering this issue, we may need to revert the changes that adopted Git LFS. |
I am having a similar issue on trying to update to 4.0.0 as well. I do have git-lfs installed but it is getting tripped up on some "missing objects" when I try to update the library using SPM (via a Tuist script)
I managed to force my way through this by temporarily setting the following in my .gitconfig
|
Same issue here. |
Thanks all for the report. We're reverting the Git LFS changes in #1835. I'll publish 4.0.1 later today that should resolve this issue. |
Released 4.0.1 with a fix for this issue. Please let us know if you're still experiencing this issue with 4.0.1. |
Yahoo, was just able to install 4.0.1 through SPM with no issues. Congrats on turning round a fix for this so quickly! |
@calda Tried to update the package via pods and spm. But facing error.
The text was updated successfully, but these errors were encountered: