FBReactNativeSpec
Cocoapods lockfile has a different hash across machines
#31698
Labels
FBReactNativeSpec
Cocoapods lockfile has a different hash across machines
#31698
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
On iOS, after running
pod install
, Cocoapods creates aPodfile.lock
. The lockfile should be checked into Version control to lock down the Cocoapods dependencies.When committing the lockfile and running
pod install
on a different machine, the hash ofFBReactNativeSpec
changes.I am raising this issue because for teams, this is a small annoyance, since you always have to either commit the hash change to an unrelated pull request or manually discard the change.
Therefore I wanted to ask if it's possible to investigate it and find a fix that causes the lockfile hashes to be reproducible across machines.
React Native version:
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
pod install
on one machine and commit thePodfile.lock
pod install
on another machine and observe that the lockfile has changed.Expected Results
The lockfile should stay the same to the Git status stays clean
Snack, code example, screenshot, or link to a repository:
As far as I know, this is reproducible on any React Native project.
The text was updated successfully, but these errors were encountered: