-
Notifications
You must be signed in to change notification settings - Fork 85
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] Always refresh provisioning profile #2125
[eas-cli] Always refresh provisioning profile #2125
Conversation
There are other cases when the provisioning profile needs to be refreshed before use and which cannot be easily validated at runtime without bigger changes in the code. It is simpler (at least for the time being) to just refresh existing profile each time See: https://exponent-internal.slack.com/archives/C9PRD479V/p1700236895524379 https://exponent-internal.slack.com/archives/C9PRD479V/p1700229660146479
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.
Looks good to me! Thanks for jumping on this 🙌
Size Change: +219 B (0%) Total Size: 42.3 MB
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2125 +/- ##
==========================================
- Coverage 54.19% 54.19% -0.00%
==========================================
Files 509 509
Lines 18663 18660 -3
Branches 3742 3741 -1
==========================================
- Hits 10113 10110 -3
Misses 8529 8529
Partials 21 21 ☔ View full report in Codecov by Sentry. |
/changelog-entry bug-fix Always refresh existing provisioning profile before use |
✅ Thank you for adding the changelog entry! |
Why
https://exponent-internal.slack.com/archives/C9PRD479V/p1700236895524379
https://exponent-internal.slack.com/archives/C9PRD479V/p1700229660146479
How
There are other cases when the provisioning profile needs to be refreshed before use and which cannot be easily validated at runtime without bigger changes in the code. It is simpler (at least for the time being) to just refresh existing profile each time
Test Plan
Run automated tests