[GH-ISSUE #399] Multiple teams found on the Developer Portal error #98

Closed
opened 2026-03-04 00:23:52 +03:00 by kerem · 7 comments
Owner

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...:

Multiple teams found on the Developer Portal, Your Terminal is running in non-interactive mode! Cannot continue from here.\nPlease check that you set FASTLANE_TEAM_ID or FASTLANE_TEAM_NAME to the right value.

Any ideas?

System configuration

  • SignTools version: 3.0.1
  • Installation type: cloudflared
  • Operating System: macOS
  • Builder type: SignTools-CI
  • Builder version: 14220bc

Additional context

Add any other context about the problem here.

Originally created by @mgcrea on GitHub (Feb 25, 2024). Original GitHub issue: https://github.com/SignTools/SignTools/issues/399 **I tried basic troubleshooting first** - [x] Updated **both** [SignTools](https://github.com/SignTools/SignTools) **and** the builder ([SignTools-CI](https://github.com/SignTools/SignTools-CI) or [SignTools-Builder](https://github.com/SignTools/SignTools-Builder)) to the latest version - [x] Read through the [FAQ page](https://github.com/SignTools/SignTools/blob/master/FAQ.md) **Describe the bug** When trying to resign, I get the following error on the CI just after the step `Registering component with Apple...`: ``` Multiple teams found on the Developer Portal, Your Terminal is running in non-interactive mode! Cannot continue from here.\nPlease check that you set FASTLANE_TEAM_ID or FASTLANE_TEAM_NAME to the right value. ``` Any ideas? **System configuration** - SignTools version: 3.0.1 - Installation type: cloudflared - Operating System: macOS - Builder type: SignTools-CI - Builder version: 14220bc **Additional context** Add any other context about the problem here.
kerem 2026-03-04 00:23:52 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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:

def fastlane_register_app(account_name: str, account_pass: str, bundle_id: str, entitlements: Dict[Any, Any]):
    my_env = os.environ.copy()
    my_env["FASTLANE_USER"] = account_name
    my_env["FASTLANE_PASSWORD"] = account_pass
+   my_env["FASTLANE_TEAM_ID"] = os.path.expandvars("$FASTLANE_TEAM_ID")

In .github/workflows/sign.yml add the value to your env at line 13

    env:
      SECRET_URL: "${{ secrets.SECRET_URL }}"
      SECRET_KEY: "${{ secrets.SECRET_KEY }}"
+     FASTLANE_TEAM_ID: "${{ vars.FASTLANE_TEAM_ID }}"      

Then in your project go to Settings > Secrets and Variables > Actions > Variables
Add a key FASTLANE_TEAM_ID with the value of your team ID

You could modify the code to work with secrets if you prefer.

<!-- gh-comment-id:1968274628 --> @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: ```diff def fastlane_register_app(account_name: str, account_pass: str, bundle_id: str, entitlements: Dict[Any, Any]): my_env = os.environ.copy() my_env["FASTLANE_USER"] = account_name my_env["FASTLANE_PASSWORD"] = account_pass + my_env["FASTLANE_TEAM_ID"] = os.path.expandvars("$FASTLANE_TEAM_ID") ``` In .github/workflows/sign.yml add the value to your env at line 13 ```diff env: SECRET_URL: "${{ secrets.SECRET_URL }}" SECRET_KEY: "${{ secrets.SECRET_KEY }}" + FASTLANE_TEAM_ID: "${{ vars.FASTLANE_TEAM_ID }}" ``` Then in your project go to Settings > Secrets and Variables > Actions > Variables Add a key `FASTLANE_TEAM_ID` with the value of your team ID You could modify the code to work with secrets if you prefer.
Author
Owner

@ViRb3 commented on GitHub (Feb 28, 2024):

This looks like something we will have to surface to the config.yml file. 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.

<!-- gh-comment-id:1969533470 --> @ViRb3 commented on GitHub (Feb 28, 2024): This looks like something we will have to surface to the `config.yml` file. 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.
Author
Owner

@ViRb3 commented on GitHub (Feb 28, 2024):

Pushed a fix in: github.com/SignTools/SignTools-CI@283a82bf2e

Update your SignTools-CI and you should be good to go.

<!-- gh-comment-id:1969902420 --> @ViRb3 commented on GitHub (Feb 28, 2024): Pushed a fix in: https://github.com/SignTools/SignTools-CI/commit/283a82bf2e9ff8b3176b886c74eee4fdcc209ba4 Update your SignTools-CI and you should be good to go.
Author
Owner

@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 involve fastlane.

Thanks for the help&patch!

subprocess.CalledProcessError: Command '('fastlane', 'produce', 'create', '--skip_itc', '--app_identifier', 'com.foo.bar.baz.mgcrea', '--app-name', 'ST com foo bar baz mgcrea')' returned non-zero exit status 1.
<!-- gh-comment-id:1969966185 --> @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 involve `fastlane`. Thanks for the help&patch! ``` subprocess.CalledProcessError: Command '('fastlane', 'produce', 'create', '--skip_itc', '--app_identifier', 'com.foo.bar.baz.mgcrea', '--app-name', 'ST com foo bar baz mgcrea')' returned non-zero exit status 1. ```
Author
Owner

@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.mgcrea is already taken by a different dev account.

<!-- gh-comment-id:1969968538 --> @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.mgcrea` is already taken by a different dev account.
Author
Owner

@mgcrea 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.mgcrea is already taken by a different dev account.

Unfortunately the output is truncated and stops abruptly:

[21:26:31]: Creating new app 'ST com foo bar baz mgcrea' on the Apple Dev Center\n\nLooking for related GitHub issues on fastlane/fastlane...\n\nFound no similar issues. To crea
Cleaning up...

But you might be onto something about the ID being taken as I've signed with another team in the past, will retry! Thanks!

<!-- gh-comment-id:1969971878 --> @mgcrea 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.mgcrea` is already taken by a different dev account. Unfortunately the output is truncated and stops abruptly: ``` [21:26:31]: Creating new app 'ST com foo bar baz mgcrea' on the Apple Dev Center\n\nLooking for related GitHub issues on fastlane/fastlane...\n\nFound no similar issues. To crea Cleaning up... ``` But you might be onto something about the ID being taken as I've signed with another team in the past, will retry! Thanks!
Author
Owner

@mgcrea commented on GitHub (Feb 28, 2024):

@ViRb3 That was it! It finally worked, thanks!

<!-- gh-comment-id:1969991260 --> @mgcrea commented on GitHub (Feb 28, 2024): @ViRb3 That was it! It finally worked, thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SignTools#98
No description provided.