Xcode Archive & Export for iOS failed with bundle install failed for Xcode 14.2 on M1

[harish-narra]

Troubleshooting

• [ ] I've searched discuss.bitrise.io for possible solutions.
• Which version of the step is effected? 1.2.3
• Is the issue reproducible with the latest version? YES / NO
• Does the issue happen sporadically, or every time? SPORADIC / EVERY TIME
• Is the issue reproducible locally by following our local debug guide? YES / NO / NOT APPLICABLE

Useful information

• FAQ
• devcenter.bitrise.io

Issue description

Bitrise info

• Build URL: Please share the build URL with us.
• Bitrise Support enabled: YES / NO
• Log:

Steps to reproduce

1. Triggerd build from bitrise
2. Archieve failed

[BenHurMartins]

+1

I am getting the same error, works locally with Xcode with the same version, but it doesn't works in Bitrise. I am pretty new with Bitrise so I didn't find the logs yet.

C/C @sehri18

[harish-narra]

@BenHurMartins am able to generate the build last week, but from yesterday onwards getting this issue, if anything found, please post here

[gustavoMarquezRefera]

same issue here, no fix so far

[harish-narra]

any update here?

[fcastaneda9725]

I've faced the same issue. I will share how I solved it.

The status error 65 is too general, you will need to look over the logs but I think you do it in your local environment, up in the logs you will find the real error that is preventing the bundle script from running. In my case:

• The first error was using pnpm but was solved using @rnx-kit/metro-resolver-symlinks
• Second error was missing dev babel dependencies like @babel/plugin-proposal-nullish-coalescing-operator or @babel/plugin-transform-arrow-functions used by one of my libraries

At this point, the local archive was working, but now still having the issue with the Bitrise archive step.

Found out that our mono repo had missing dependencies at the moment to archive, so I had to add some extra command lines for my Script step remove some dependencies and install again during a new build with Turbo and the problem was solved.

Make sure you have your script right under ProjectName -> Build Phases -> Bundle React Native code and images:

set -e

WITH_ENVIRONMENT="../node_modules/react-native/scripts/xcode/with-environment.sh"
REACT_NATIVE_XCODE="../node_modules/react-native/scripts/react-native-xcode.sh"

/bin/sh -c "$WITH_ENVIRONMENT $REACT_NATIVE_XCODE"

I know that my solution was particular, but I can suggest you go deeper into the logs and you will find the real error that it's preventing react-native-xcode.sh to run.

[psvnanda]

+1. Is there any proposed workaround?

[bsamban]

Is there any fix for this issue ?

[RichardLima]

In my case, I fixed it after analyzing: xcodebuild-archive.log, and identified that the bitrise machine started to use an updated node version and that it has the problem: openssl-legacy-provider. :)

[sufyansalim]

any update on this issue?

[sufyansalim]

In my case, I fixed it after analyzing: xcodebuild-archive.log, and identified that the bitrise machine started to use an updated node version and that it has the problem: openssl-legacy-provider. :)

how can i do that i new to bitrise?

[RichardLima]

@sufyansalim Workflow tab > choose your workflow > after the xcode archive step add the "Deploy to bitrise.io" step > save > run your failed workflow again > after finishing/failing > enter your build > artifacts > xcodebuild-archive.log

[bitrise-coresteps-bot]

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

[bitrise-coresteps-bot]

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.