Built an app and set up CircleCI, all worked well.
Client needed to transfer app to new AppStoreConnect account, so we did that. Now the fast lane builds fail every time – Errors are vague enough to be useless. We’re stuck.
We thought it was a code signing issue, but that doesn’t seem to be the case. Logs attached below:
Transferring an app to a new App Store Connect account can sometimes lead to unexpected issues, especially with continuous integration setups like CircleCI. It’s frustrating when builds start failing without clear error messages. Given that you’ve ruled out code signing as the issue, it might be worth double-checking the app’s provisioning profiles and entitlements to ensure they align with the new account. Troubleshooting app development challenges like this can be tricky, but reviewing all settings related to the app transfer could help pinpoint the root cause.
Transferring an app to a new App Store Connect account can sometimes cause issues that aren’t easy to spot, especially when using tools like CircleCI for continuous integration. If code signing isn’t the problem, it’s a good idea to take a closer look at your provisioning profiles, entitlements, and any linked certificates to make sure they match the new account details. Even small mismatches can cause builds to fail without showing clear errors. A good mobile app development company usually runs through all these settings step by step after a transfer to make sure everything works smoothly. Going over the app’s setup from top to bottom could save you a lot of time and get your builds running again.