-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[resign] fix entitlements merging when changing team while resigning #18713
[resign] fix entitlements merging when changing team while resigning #18713
Conversation
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
The contents of this PR were approved, and all author CLAs have been signed a couple of times now in the other linked PRs. |
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.
@silvervest Hello! Do you mind appending the changelog to the top of the file with a summary of the changes here? 😊 After that we can get this merged 💪
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
Done and done @joshdholtz, cheers! |
@silvervest Thank you! Will smash the merge button when tests are done running 💪 |
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.
This looks good to me! Thank you so much for reviving this PR (again (again)) ❤️ Really appreciate it!
Great! And just for the official merge record, want to provide thanks to @kapfab for actually authoring this change in the first place 🥂 |
You’re welcome. I just hope this PR will finally find its way to a release. And in case this is needed, I’ll consent to the CLA. |
@googlebot I consent. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Just had a quick look at the changes. I think lines 801-808 (replacement of App ID and Team ID) could be removed, as lines 848-858 do the same on the whole entitlements file (which indeed seems a better option as other entitlements values could reference the App ID or Team ID): fastlane/sigh/lib/assets/resign.sh Lines 801 to 808 in abe50be
fastlane/sigh/lib/assets/resign.sh Lines 848 to 858 in abe50be
Also, AFAIR, the fastlane/sigh/lib/assets/resign.sh Line 791 in abe50be
|
@silvervest, did you voluntarily rollback you previous commit (dd77fef)? Also, is there a reason why fastlane/sigh/lib/assets/resign.sh Line 827 in abe50be
I’m a bit worried on this specific change… |
Hmm! Not voluntarily. I have no idea how that happened, actually.
That appears to have been a typo from the very first merge conflicts I "fixed" in your original PR. Likely as the change to I'll resolve these ASAP and submit another PR. Thanks for catching those @kapfab! |
Actually @kapfab I'm looking at this again and I can't see this commit reverted? The file is up to date with this change in master? |
My mistake, I probably saw that on silvervest@caf995e when I was looking for the origin of the certificate-related change. |
I am really confused by this. I didn't remove this change, and if you look at the .patch of this pull request, that change is definitely in there, but it wasn't part of the merged changes, nor does it show on the files changed tab. I am at a loss... |
It was part of my initial commit that never reached the master branch (until today!), it probably got lost by someone else months ago during one of the different merges that occurred since. Not a big deal, that might be fixed in a future PR. |
Hey @silvervest 👋 Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉 Please let us know if this change requires an immediate release by adding a comment here 👍 |
Congratulations! 🎉 This was released as part of fastlane 2.184.0 🚀 |
Hi @silvervest , I updated to the latest Fastlane, but this entitlement is invalid for me. Can you have a look? com.apple.developer.icloud-container-environment |
WARNING: Changing team while resigning |
Which value did you expect and which one did you get? |
The only reason I can see for such a behaviour would be that your app did not include this entitlement but your provisioning profile did, which is quite unusual.
|
fastlane/sigh/lib/assets/resign.sh Line 833 in abe50be
In this line, I printed it out empty, adjusted the code here locally, and everything was OK ENTITLEMENTS_VALUE=$NEW_ICLOUD_ENV |
I still do not understand how you original app ended up in this state. |
You need to try it once, I've found the cause of the problem ENTITLEMENTS_VALUE=$NEW_ICLOUD_ENV It works for me. |
* Fix the way app entitlements are extracted (see fastlane#18713) * Homogenise sed invocations (following fastlane#17075)
After some investigation, your issue is related to the way entitlement values are extracted (what the lost Your workaround might work (even though you feed the — quite permissive — I will open a new PR with a less specific fix. Could you try to resign your app with this change (kapfab@8e98846) to confirm this solves your issue? |
After my test, the problem was solved perfectly. And I deliver to Appstore connect. thank you. gem "fastlane", :git => "https://github.com/kapfab/fastlane", :branch => "resign_app_entitlements_fixes" |
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validMotivation and Context
These are the changes from #12131 updated to master and with merge conflicts resolved. Please see that issue for more in-depth detail.
This was resubmitted again due to lose head repository branch, but is the same changes.
Description
Testing Steps
supersedes #12131 and #15388