You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the same npm version of react-native-heap package, every time we run pod install a new checksum is generated. This behavior is odd and causing our CI machines to raise alerts because it's detected new changes in lock files. Do we know the reason for this issue that does not happen with other packages we use? Thank you
The text was updated successfully, but these errors were encountered:
I haven't tried it yet, but I'm guessing we need to change line 3 of the Podspec from: json = File.read(File.join(__dir__, "package.json"))
To: json = File.read(File.join("$PODS_TARGET_SRCROOT/../../", "package.json"))
[HEAP-48203](https://heapinc.atlassian.net/browse/HEAP-48203)
Reported in #400, the podspec was generating a new checksum on different devices. The issue is that we were using `path => '.'` instead of `:path => '.'`, which caused the `path` variable to expand as a key. I've updated to the source repository to match what the modern template does. It doesn't affect behavior, since `source` is ignored for local podspecs.
Using the same npm version of react-native-heap package, every time we run
pod install
a new checksum is generated. This behavior is odd and causing our CI machines to raise alerts because it's detected new changes in lock files. Do we know the reason for this issue that does not happen with other packages we use? Thank youThe text was updated successfully, but these errors were encountered: