-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
Podfile hashes encode absolute file path #38492
Comments
Here's also another earlier PR that tried to switch from absolute to relative paths in order to avoid this issue: |
Seems like the absolute path in header_mappings_dir was introduced in v0.72.2 |
That line is in: |
Closing as @cipolleschi handled all the cases where Podfiles where referencing absolute paths |
Description
After upgrading to 0.72.x, we're seeing an issue generating Podfile.lock with some of the new packages added. Specifically:
My theory is that this is due to absolute paths to files on my machine are being used as part of the checksum generation, which means it will always be different on every computer.
It is not simply an issue of running
pod update {pod_name}
that usually works when the problem is just that the podspec file has been changed without bumping the version number.React Native Version
0.72.3
Output of
npx react-native info
Steps to reproduce
pod install
and commit the podfile.lock.If you run
pod install --deployment
you'll get an error because the hashes for the listed dependencies above have changed, and if not, the Podfile.lock will just keep changing between each computer.Snack, code example, screenshot, or link to a repository
Here's a previous commit that fixed a similar issue in an earlier version of react native:
bdfe2a5
And a suggested patch for that earlier issue:
#31121 (comment)
The text was updated successfully, but these errors were encountered: