-
Notifications
You must be signed in to change notification settings - Fork 134
[eas-cli] fix CapabilityModel creation and syncing #3088
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
[eas-cli] fix CapabilityModel creation and syncing #3088
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Size Change: -2.34 kB (0%) Total Size: 53.5 MB
|
de26105
to
b4d65ea
Compare
9e67180
to
9dab486
Compare
b4d65ea
to
6210218
Compare
9dab486
to
73ecbb2
Compare
6210218
to
4426121
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3088 +/- ##
==========================================
+ Coverage 51.77% 51.77% +0.01%
==========================================
Files 607 607
Lines 24385 24385
Branches 5120 5119 -1
==========================================
+ Hits 12622 12624 +2
+ Misses 10713 10712 -1
+ Partials 1050 1049 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
4426121
to
045b03d
Compare
Subscribed to pull request
Generated by CodeMention |
60d63d6
to
47f6f53
Compare
47f6f53
to
3893477
Compare
a8be45c
to
a92141d
Compare
3893477
to
081170b
Compare
1588bfc
to
65de17f
Compare
081170b
to
da14035
Compare
65de17f
to
a88897b
Compare
da14035
to
8f8244a
Compare
8f8244a
to
90fa44c
Compare
✅ Thank you for adding the changelog entry! |
Why
The current implementation of capabilities syncing can lead to provisioning profiles becoming invalid. This PR refactors the syncing process to avoid this issue by making the following improvements:
closes #1069
closes #1445
How
I refactored the capability syncing logic to:
Test Plan
easd
command below is from https://github.com/expo/eas-cli/blob/main/CONTRIBUTING.md#development.To best test this locally, have an iOS app with
(1) no capabilities enabled. Enable some capabilities in
app.json
and run prebuild. iCloud, Apple Sign In, app groups, or"com.apple.developer.default-data-protection": "NSFileProtectionComplete / ..."
are of special interest, but any will do.OR
(2) a buch of capabilities already enabled
using this app, run
easd build -p ios
TWO times. Confirm that the first build creates new capabilities on your app bundle (https://developer.apple.com/account/resources/identifiers/list) and provisioning profiles (if any). Confirm the second build passes and doesn't require any provisioning profile changes.Finally, change the capabilities, and again run
easd build -p ios
twice to confirm no capabilities / provisioning profiles are changed on the second run (that's what should happen on the first run).