Match development with Appstore Connect API KEY fails due unexpected token error if there are more 18 bundle ids in matchfile

[Dmitry-Pliushchai]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

We started getting the unexpected token error when running match(force_for_new_devices: true,readonly: false). It worked well with the same api key but stopped working for us 2 weeks ago or so. We also tried it with new api key with "App Manager" role but it didn't help. The rest fastlane commands work well with api key (haven't tried match appstore yet)

Command executed

match(
        force_for_new_devices: true,
        readonly: false
      )

Complete output when running fastlane, including the stack trace and command used

Successfully decrypted certificates repo
[18:22:09]: Verifying that the certificate and profile are still valid on the Dev Portal...
[18:22:09]: Creating authorization token for App Store Connect API

+----------------------------------------+
| Lane Context |
+---------------+------------------------+
| ENVIRONMENT | development |
| PLATFORM_NAME | ios |
| LANE_NAME | ios install_provisions |
+---------------+------------------------+
[18:22:10]: unexpected token at '

<title>403 Forbidden</title>

403 Forbidden

---

Apple '

[WayneF11]

It looks like you’re encountering a 403 Forbidden error with Fastlane’s match command. Here’s what you can do: aarp membership login

1. Check API Key: Ensure your API key has the correct permissions and is not expired.
2. Update Fastlane: Make sure Fastlane is updated to the latest version as this might be a known issue that has been resolved.