-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(eas-cli): Ensure non-exempt encryption status #2843
feat(eas-cli): Ensure non-exempt encryption status #2843
Conversation
Size Change: -1.65 kB (0%) Total Size: 53.4 MB
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2843 +/- ##
==========================================
+ Coverage 52.78% 52.85% +0.07%
==========================================
Files 585 586 +1
Lines 22765 22803 +38
Branches 4746 4756 +10
==========================================
+ Hits 12014 12050 +36
- Misses 9812 9814 +2
Partials 939 939 ☔ View full report in Codecov by Sentry. |
Subscribed to pull request
Generated by CodeMention |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome! thanks for working on it 🙏
few comments:
i approve of the approach, will leave the actual code review up to @szdziedzic |
✅ Thank you for adding the changelog entry! |
Hey @EvanBacon , just to let you know: I'm having a dynamic app.config.ts. When I try to run my build, I get the following error:
The solution is of course to add to my app.config.ts manually:
However: I'm not really happy that the build process just errors and does not give clear instructions to the user what to do. |
Why
Apple requires the non-exempt encryption status be defined on every build before it can be submitted to TestFlight or app review. We can use the Info.plist flag to only ask users one time and reuse that answer for every build. This is a better version of expo/expo#34487
Prompting in the CLI saves users six clicks in App Store Connect for every iOS build.
How
I copied the bundle identifier prompting logic to a new function for setting non-exempt encryption, made it more optional, and added it to
eas build -p ios
.If the user indicates that they use non-exempt encryption then we won't write anything this will enable them to see the in-depth warnings in ASC about this option. They can still skip the prompt by manually adding the value to their app.json.
Test Plan
eas build -p ios
-> prompted "app uses standard encryption?" -> enter / Y -> app builds and doesn't ask again.