I think I’ve run into a bug in EAS Build when using packages imported with the yarn
file: synax, e.g. to handle patched dependencies.
I am trying to implement the change at https://github.com/expo/expo/pull/16670 and since there is no release including this PR yet, I needed to make a tarball from the cherry-picked change. I re-used the filename for the tarball between versions, and EAS Build failed with
[stderr] error Integrity check failed for "expo-in-app-purchases" (computed integrity doesn't match our records...
I don’t think there’s any way to make yarn generate these checksums in the lockfile for file paths.
yarn --update-checksums does nothing, there’s no checksum in the lockfile at all.