mirror of
https://github.com/SignTools/SignTools.git
synced 2026-04-26 18:35:55 +03:00
[GH-ISSUE #399] Multiple teams found on the Developer Portal error #98
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SignTools#98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mgcrea on GitHub (Feb 25, 2024).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/399
I tried basic troubleshooting first
Describe the bug
When trying to resign, I get the following error on the CI just after the step
Registering component with Apple...:Any ideas?
System configuration
14220bcAdditional context
Add any other context about the problem here.
@markrassamni commented on GitHub (Feb 28, 2024):
Here is how I solved this issue when I had it
In sign.py line 373 add this:
In .github/workflows/sign.yml add the value to your env at line 13
Then in your project go to Settings > Secrets and Variables > Actions > Variables
Add a key
FASTLANE_TEAM_IDwith the value of your team IDYou could modify the code to work with secrets if you prefer.
@ViRb3 commented on GitHub (Feb 28, 2024):
This looks like something we will have to surface to the
config.ymlfile. I don't have time now, but will try to look at this soon.EDIT: Actually, we should be able to automatically determine the team id from the certificate and pass it as an environment variable in Python. Will confirm later today if it's so trivial to fix.
@ViRb3 commented on GitHub (Feb 28, 2024):
Pushed a fix in:
github.com/SignTools/SignTools-CI@283a82bf2eUpdate your SignTools-CI and you should be good to go.
@mgcrea commented on GitHub (Feb 28, 2024):
@ViRb3 can confirm that it works and I no longer get the same error, unfortunately signing still does fail at a later stage (at
Signing with entitlements:), not sure if it is related but it does involvefastlane.Thanks for the help&patch!
@ViRb3 commented on GitHub (Feb 28, 2024):
There should be more detailed logs from fastlane that tell you exactly what's wrong. If I were to guess, maybe the bundle id
com.foo.bar.baz.mgcreais already taken by a different dev account.@mgcrea commented on GitHub (Feb 28, 2024):
Unfortunately the output is truncated and stops abruptly:
But you might be onto something about the ID being taken as I've signed with another team in the past, will retry! Thanks!
@mgcrea commented on GitHub (Feb 28, 2024):
@ViRb3 That was it! It finally worked, thanks!