The .shasum file used by Apollo 0.16 has content like this: 13febaa462e56679099d81502d530e16c3ddf1c6c2db06abe3822c0ef79fb9d2 /Users/USER/APP_NAME/TARGET_NAME/../Pods/Apollo/scripts/apollo.tar.gz
We commit the Pods/ directory to our project repo. Because the tarball path is absolute it'll differ between machines that check out the project and run the build phase. This means that the path in the .shasum file is changing as we work on our project and so we need to choose from: manually revert the change, accept that the file will be in our diffs, gitignore it, etc.
I was thinking this tarball path could be relative to PODS_ROOT when it's been integrated with CocoaPods, which should avoid the root cause of different project checkout paths on different computers. Would need to make sure a change for this doesn't affect the other ways of integrating Apollo. Wondering if you have a preferred way to solve this?
The .shasum file used by Apollo 0.16 has content like this:
13febaa462e56679099d81502d530e16c3ddf1c6c2db06abe3822c0ef79fb9d2 /Users/USER/APP_NAME/TARGET_NAME/../Pods/Apollo/scripts/apollo.tar.gzWe commit the Pods/ directory to our project repo. Because the tarball path is absolute it'll differ between machines that check out the project and run the build phase. This means that the path in the .shasum file is changing as we work on our project and so we need to choose from: manually revert the change, accept that the file will be in our diffs, gitignore it, etc.
I was thinking this tarball path could be relative to PODS_ROOT when it's been integrated with CocoaPods, which should avoid the root cause of different project checkout paths on different computers. Would need to make sure a change for this doesn't affect the other ways of integrating Apollo. Wondering if you have a preferred way to solve this?