Closed abekerau closed 1 year ago
We believe we're seeing this error too, any thoughts or movement on this issue at all?
@JackOddy Hi, it looks like we are stuck on this step, there is no progress on this issue.
@abekerau I have fixed the above issue by selecting the warning banner on the bitrise, which took me to the section you see in the screenshot; then, I selected the M1 option and saved it. After that, all the builds were built successfully till now.
@abekerau I have fixed the above issue by selecting the warning banner on the bitrise, which took me to the section you see in the screenshot; then, I selected the M1 option and saved it. After that, all the builds were built successfully till now.
@niyogakiza Yes, we followed the same way, and our stack switched to M1 (the build didn't work) and then switched to Rosetta 2 (the build didn't work). So I kept fixing this issue for the Bitrise build for Rosetta 2, because I don't have an M1 machine for local tests.
We're also stuck on the same step, same error, with Rosetta.
What's weird is our exact same commit works with a slightly different workflow - one that uploads to the app store via the api-key
method than the apple-id
method.
I fixed this by removing automatic code signing. If the workflow is using apple-id
it will fail. If you're using api-key
it'll work just fine.
Can someone at Bitrise (@tothszabi ?) update us here when you guys fix it on your end? Thanks!
We're using an enterprise account, so we have to use apple-id
. This is a blocker for us and we've had to revert back to manually managing code signing.
Troubleshooting
Useful information
Issue description
So due to the migration of Intel workflows to M1 machines there was a problem with bundle install: In Gemfile: fastlane was resolved to 2.212.1, which depends on json
And the end:
There is our Gem File:
Bitrise info
Steps to reproduce
Run Xcode Archive & Export step