Link app to EAS project for iOS builds#27
Merged
Conversation
Adds extra.eas.projectId (written by `eas init`) plus an explicit `owner` so EAS production/TestFlight builds resolve the correct Expo account across machines. No runtime impact — build config only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Persists the EAS linkage created by
eas initso iOS production / TestFlight builds work from any checkout:extra.eas.projectId=1cd8338b-4ead-4ad0-b90f-32d0ff324f7a(Expo project@hyperion-studio/redline-id)owner: "hyperion-studio"so EAS resolves the correct Expo account (the repo's Apple bundle id stayscom.burkben.redlineid)Why
eas initwrites the projectId into the localapp.jsononly. Committing it (plusowner) makes the linkage durable and unambiguous across machines and CI — required foreas build/eas submit.Risk
Build/config metadata only — no runtime or app behavior change. Not consumed by the JS bundle.