[expo-updates] Use --profile in fingerprint:generate and runtimeversion:resolve to fetch related environment variables

[tfcornerstone]

Summary

Currently when using eas build, the local fingerprint uploaded to EAS is different from the output of expo-updates fingerprint:generate locally. The reason for this is the difference in env variables. No reason to maintain environment variables in different places when it can be read from the eas.json profile.

What platform(s) does this occur on?

Android, iOS

SDK Version

51.0.0

Environment

N/A

Minimal reproducible example

Try to build using EAS with environment variables and compare the fingerprint to normal expo-updates fingerprint

[Kudo]

hi there! could you share your build id? e.g. https://expo.dev/accounts/XXX/projects/XXX/builds/ee1bad22-a2c6-4c10-8ef2-281ea15980ee, the ee1bad22-a2c6-4c10-8ef2-281ea15980ee is the build id.

[tfcornerstone]

@Kudo

2baa711b-ff01-4229-ab24-fdf4f7ebd9c8

I resolved the issue by setting the env variables of local to match the env variables in eas.json production profile.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[mirague]

This sounds like a pretty good addition, or is there a more "eas"-like way to achieve this?

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.

[mirague]

@Kudo any more insights or initiatives planned to align fingerprints between local and cloud builds?

[Kudo]

@mirague ideally local/cloud fingerprint should be aligned. would love to hear your use cases and figure out how fingerprint is inconsistent between local and cloud