eas build -p ios | Fastlane build failed with unknown error #1079
Comments
|
Same issue here with same troubleshooting. It was working not long ago for me too. I assume it's Expo's build servers then? |
|
You are depending on some third-party library that provides prebuild binaries build on a newer version xcode than expo servers have. The only option is to downgrade those libraries. closing issue for now |
|
It looks like we will need new code for next SDK, so we will probably update latest image next week |
|
Thanks!
Does anyone know how to easy detect the third-party lib compiled with the newest XCode?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Wojciech Kozyra ***@***.***>
Sent: Friday, April 22, 2022 1:37:48 PM
To: expo/eas-cli ***@***.***>
Cc: Luca Agostini ***@***.***>; Author ***@***.***>
Subject: Re: [expo/eas-cli] eas build -p ios | Fastlane build failed with unknown error (Issue #1079)
It looks like we will need new code for next SDK, so we will probably update latest image next week
—
Reply to this email directly, view it on GitHub<#1079 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXEMV5IXN77AGVMQSTOHOYTVGKFQZANCNFSM5T7VESWQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
For anyone to not to go trouble going through all third-party library, I raised the macos image on azure pipeline to macos-12 and it was solved. |
|
the latest image is now using xcode13.3 |
|
I'm a beginner and tried to compile the HelloWorld demo sample but no success to publish to apple store. And the ios Xcode log (lasts lines because its 10k lines !! Not succees to find which library was in cause) : and package.json : and eas.json : |
|
@frankbret are you building locally ? then what is your xcode version ? |
|
No, not locally, I don't have a mac and this is why I tried this ReactNative/Expo/Eas thing. I waited and after minutes the console said: Glad to know there is a local way to compile if I buy a mac. |
|
Answered myself, with a little help from this thread somehow related. And build with : (just to do the same with "production" profile (probably)) And the reason is here Latest = 13.3 default = 13.0 !!! |
## ✅ What's done - [x] `expo upgrade 45` - [Changelog](https://github.com/expo/expo/blob/main/CHANGELOG.md#4500--2022-04-25) - Since React Native Elements depends on the react-native-safe-area-context 3.x, only react-native-safe-area-context is left as 3.3.2 - [x] Apply changes of [expo-template-bare-minimum](https://github.com/expo/expo/commits/sdk-45/templates/expo-template-bare-minimum) - [x] Apply changes of [ReactNativeFlipper.java](https://github.com/facebook/react-native/commits/0.68-stable/template/android/app/src/debug/java/com/helloworld/ReactNativeFlipper.java) - [x] Add patch for React Native Elements type error - [x] Fix lint error(flatten of AnimatedStyle and ViewStyle) - [x] Update snapshots - [x] Fix autoCompleteType in TextInputProps changed to autoComplete. - [x] Fix AppState cleanup - [x] Fix SelectPickerItems test to use useFakeTimers and runAllTimers - [x] Add option `requireConfirmation` to local authentication demo - [x] Add eslint-plugin-deprecation to detect deprecated - [x] Set "EXCLUDED_ARCHS[sdk=iphonesimulator*]" = "" - [x] Add ResetEditText to styles.xml - [x] Bump up macOS to 12 and Xcode to 13.3.1 on ci to resolve the following errors - `❌ ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '1316.0.21.2.3_0' Reader: '1300.0.29.30_0')', using libLTO version 'LLVM version 13.0.0, (clang-1300.0.29.30)' for architecture arm64` - Similar ref. expo/eas-cli#1079 - [x] Remove cache pods restorekeys on c - [x] Remove cleanBuildCache from android cmd in reset-cache - [x] Bump up tool versions | Tool | from | to | |-----|-----|----| | Node.js | 16.14.2 | 16.15.1 | | Ruby | 3.0.3 | 3.1.2 |
|
How to fix it on BigSur 11.6.7 + Xcode Version 13.2.1 (13C100) ? |
|
I'm getting this error as well on Expo's build servers I copied the and my The |
|
I'm using Expo Bared Project, facing the same issue |
|
@xubmuajkub me, too. Using Expo 46, ejected app, MacBook M1, Xcode |
|
Same issue here. Using expo sdk 46 and running eas build with --local flag on Azure pipeline using 'macos-latest' image. |
|
@PingvinB That means that the Xcode version is too old. |
|
Oh. I will try to make it use a newer version then. Thank you! Edit: What is the minimum required version of Xcode for sdk 46? Edit 2: I changed the image in the pipeline from 'macOS-latest' (which apparently is macOS 11) to 'macOS-12'. |
Do you have an example of how to change the image pipline in the configuration settings? |
|
I'm experiencing this today, we haven't added any non-Expo dependencies since the last successful build, and all of those dependencies were added using Expo's CLI, so they should be using compatible versions. |
|
Dependencies added (confirmed via Git diff): |
|
We did another build without making any changes at all and it worked, so maybe an intermittent issue somewhere/somehow? Do not know enough about EAS's architecture to say. |
|
Hi everyone! I come accross this error too and change the image used to build the application. But once build, the IOS application systematically crashed. Here is the log, maybe someone may have an idea I just move to Expo 45 and here is my package.json |
|
The error was thrown by incompatibility with a non expo-managed javascript library. In my case it was react-native-keyboard-aware-scroll-view. |
This causes apple to flag our code because adds development API calls it seems? The app references non-public selectors in YOUR_APP: _isKeyDown, _modifiedInput, _modifierFlags. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. |
|
I had the same problem, do a general cleanup in the credentials section of your project in your expo.dev account and then do a rebuild. |
|
Removing accent on name in app.json solved it for me
|
Build/Submit details page URL
No response
Summary
I was able to properly create .ipa until last week, but now I get this error in FastLane during linking:
I tried to compile it with image="latest" with no luck.
Android build is working properly.
I also tried to archive the project locally with XCode13.3 after "expo prebuild --clean -p ios" and it worked.
Managed or bare?
Managed
Environment
expo-env-info 1.0.2 environment info:
System:
OS: macOS 12.2.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Watchman: 2021.11.15.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 13.3/13E113 - /usr/bin/xcodebuild
npmPackages:
babel-preset-expo: 9.0.2 => 9.0.2
expo: ^44.0.6 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
eas-cli: 0.51.0
expo-cli: 5.3.2
Expo Workflow: bare
Error output
No response
Reproducible demo or steps to reproduce from a blank project
This is my eas.json:
{ "cli": { "version": ">= 0.47.0" }, "build": { "development": { "developmentClient": true, "distribution": "internal" }, "preview": { "distribution": "internal" }, "production-ios": { "ios": { "image": "latest" }, "distribution": "store", "releaseChannel": "production.ios-1.7.1" } }, "submit": { "production": {} } }I queued the build with:
The text was updated successfully, but these errors were encountered: