Closed keitaito closed 2 years ago
Hi @keitaito,
Thanks for bringing this up and also including additional resources! What is the use case for cloning the full repo? Would it be sufficient to partially clone the repo with a shallow clone?
Thanks!
We're facing the same issue by integrating the SDK with Swift Package Manager. Swift Package Manager is downloading the whole repository when it's not in the local disk cache or differs. This is slowing down our build times, locally and on our build agents, and therefore decreasing the development efficiency of our developers too.
Hi @martinknabbe,
When integrating the SDK with Swift Package Manager, are you using our new repo optimized for SPM? You can follow the integration instructions here and use the url https://github.com/braze-inc/braze-ios-sdk
when importing via SPM - this should significantly improve your import speeds.
Thanks!
Hi @hokstuff,
thank you for this tip. I didn't know about it. I'll give it a try. 👌
Hi @keitaito,
Are you still experiencing this issue, or are the workarounds provided above sufficient?
Best, Daniel
Hi @keitaito,
Thanks for filing the information in this thread and submitting some suggestions. I'm updating here because we are planning to address this issue more holistically in our upcoming Swift SDK, since that won't result in erasing git history which is irreversible and may affect some of our clients. Please reference this thread to sign up for our early access program and stay tuned for additional updates regarding the new SDK!
Since there are no immediate follow ups for this issue, I am closing it out. Thank you for understanding!
Report
Hi, we noticed the appboy-ios-sdk repo size is currently super large when git cloning.
Specifically .git/objects/pack directory takes
Specifically pack-ab495c407ec30a505157c76a340eb3c715ff1ea8.pack file takes 1.3GB.
It seems the issue is similar to the issue reported on 18F/C2 repo. Potential relevant Stack Overflow question.
We are guessing you used to ship binaries of the library in a checked in Pods folder in an example. They have since been removed, but multiple versions of the library still exists in the git history.
Would it be possible for you to update the git history in the repo on your end?
Describe your environment.
What did you do?
The issue can be reproduced by just git cloning the repo.
What did you expect to happen?
Repo size is not large. Ideally less than 15 MB or something.
What happened instead?
The repo size is super large. About 1.42 GB.
Steps to reproduce
The issue can be reproduced by just git cloning the repo.