-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(:fire:) ARCHIVE FAILED The following build commands failed: PhaseScriptExecution [CP-User]\ [RNFB]\ Crashlytics\ Configuration #5789
Comments
The issue has been solved! Apple M1 was the culprit. Fixed by installing Thanks! |
Hi there! Building on M1 is difficult, but it definitely works now. You don't need rosetta, I worked with the core team here facebook/react-native#31941 and finally resulting in facebook/react-native@ac4ddec#diff-adcf572f001c2b710d14f409c14763f1a50b08369b3034548f1602685d21f67fR219-R248 - you can ingest those in your Podfile and it will work - or upgrade to react-native 0.66 (via upgrade_helper) and include the Podfile call to that workaround they added for now Rosetta has it's own problems and since it's kind of a dead-end solution I wouldn't recommend going there, if you do have rosetta-related problems there will be zero interest in fixing them vs fixing actual M1 native issues |
@mikehardy I just bumped into this issue. Got a new M1 laptop and was trying to get as far as I can get without installing Rosetta 2 at all.
You do! arm64 builds for apps with Crashlytics fail if Rosetta 2 is not installed on the machine, because It would be great if this could be documented somewhere :) |
Oh interesting. I've never tried actually uninstalling Rosetta2 completely, that seems counterproductive. I guess I should be more specific: You do not need your shell / cocoapods / Xcode all that (your toolchain) running under Rosetta2. And in fact there was a fair bit of collaboration to specifically warn people off it - first on Discord amongst myself and some others trying to get M1s to work well, then concretely in: facebook/react-native#32296 There's also microsoft/vscode#116763 which was fun ;-) I do expect Rosetta2 to be installed though, I can't imagine trying to run without it, yet. I just checked firebase-ios-sdk and I did not see any issues logged upstream about this. you might try logging this there to see if they can make it a universal binary I do believe Rosetta2 is not required for any part of the actual app build though, if you'll go with me and draw a fine line between "app build" and "tangential things like symbol upload" |
Thanks! I've created this issue: firebase/firebase-ios-sdk#8965 |
Issue
iOS Archive fails with error
TelldusLiveApp-TelldusLiveApp.log
This issue happens only in the CI, in my local machine it works fine.
We use fastlane to build and release the app in the CI.
It is the fastlane
gym
phase that fails.CI Machine:
System:
OS: macOS 11.4
CPU: (8) arm64 Apple M1
Memory: 989.61 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Project Files
Javascript
Click To Expand
package.json
:firebase.json
for react-native-firebase v6:iOS
Click To Expand
ios/Podfile
:AppDelegate.m
:Android
Click To Expand
Have you converted to AndroidX?
android/gradle.settings
jetifier=true
for Android compatibility?jetifier
for react-native compatibility?android/build.gradle
:// N/A
android/app/build.gradle
:// N/A
android/settings.gradle
:// N/A
MainApplication.java
:// N/A
AndroidManifest.xml
:<!-- N/A -->
Environment
Click To Expand
react-native info
output:(CI Machine)react-native-firebase
version you're using that has this issue:Firebase
module(s) you're using that has the issue:TypeScript
?N
React Native Firebase
andInvertase
on Twitter for updates on the library.The text was updated successfully, but these errors were encountered: