Borahm
commented
8 months ago Same issue here! It was working totally fine yesterday
Open Albert-Gao opened 8 months ago
Borahm
commented
8 months ago Same issue here! It was working totally fine yesterday
burrrrrr
commented
8 months ago Same here
alanwsh
commented
8 months ago same here
erdemgonul
commented
8 months ago Same problem for 1 week.
It started after updating to MacOS Sonoma and Xcode-15.0.1. I can't revert MacOS and Xcode versions. In EAS build it works because of stable versions.
Note: Only IOS Simulator developmentClient build works fine
Raushan12345comp
commented
8 months ago I am also facing same issue after upadating xcode version to 15.0
konteris
commented
8 months ago FIx that worked for me:
alex-k8
commented
8 months ago Same issue here, any workaround? The above one didn't help.
mhendyl
commented
8 months ago Same problem for 1 week.
It started after updating to MacOS Sonoma and Xcode-15.0.1. I can't revert MacOS and Xcode versions. In EAS build it works because of stable versions.
Note: Only IOS Simulator developmentClient build works fine
Same issue here, and I decide to downgrade my Xcode into 14.3.1 you can download that here https://developer.apple.com/download/all/?q=xcode
szdziedzic
commented
8 months ago Hi,
Does this issue only occur for you when running builds with the --local flag or also on EAS servers?
This message seems to be only a warning. I believe that you should be able to find the true error in the Xcode logs (it's not the same as the Run Fastlane phase logs). When it comes to debugging it locally I think that you can try to use the env vars described in
https://docs.expo.dev/build-reference/local-builds/#use-local-builds-for-debugging to prevent the working dir cleanup and to specify the working directory path. It should allow you to find Xcode logs inside of the working dir and take a look at them. Maybe you will find some other helpful information there.
Let me know if it helps!
If you run build on EAS cloud you should be able to see the Xcode logs at the very bottom of a build page.
szdziedzic
commented
8 months ago Unfortunately, I wasn't able to replicate the issue on my test app both locally and on the EAS server.
szdziedzic
commented
8 months ago Also, I'm not saying that it is the root cause of the issue, but it might be helpful to fix the warning displayed in the expo doctor logs for your project
szdziedzic
commented
8 months ago Ok, so I was able to get the same warning in the Run Fastlane phase, but it was just a warning and my app compiled successfully overall. If I run a EAS_LOCAL_BUILD_SKIP_CLEANUP=1 EAS_LOCAL_BUILD_WORKINGDIR=/Users/szymondziedzic/expo/turtle-v2-example/workdir npx eas-cli@latest build --local --platform ios --profile production command I'm able to see my Xcode logs in /Users/szymondziedzic/expo/turtle-v2-example/workdir/logs directory. I believe that in these logs you will find the true root cause of your issues.
erdemgonul
commented
8 months ago Ok, so I was able to get the same warning in the
Run Fastlanephase, but it was just a warning and my app compiled successfully overall. If I run aEAS_LOCAL_BUILD_SKIP_CLEANUP=1 EAS_LOCAL_BUILD_WORKINGDIR=/Users/szymondziedzic/expo/turtle-v2-example/workdir npx eas-cli@latest build --local --platform ios --profile productioncommand I'm able to see my Xcode logs in/Users/szymondziedzic/expo/turtle-v2-example/workdir/logsdirectory. I believe that in these logs you will find the true root cause of your issues.
After delving into the logs following @szdziedzic comments, I noticed some warning logs regarding the minimum deployment target for iOS in Firebase packages. I attempted to resolve this issue by adding "deploymentTarget": "13.0" to the app.json build properties, but it didn't work for the pods used in the project. To address this problem, after a bit of googling, I came across a script that should be added to the Podfile.
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
end
endIn the Expo managed workflow, we don't have direct access to certain folders as they are managed internally, unlike in the bare workflow. After some research, I discovered the npx expo prebuild command. This command generates the ios folder similar to the React Native CLI, allowing you to make edits to the necessary iOS files. After making your changes, you can build your iOS project using Xcode.
By the way, in the end, adding entries to the Podfile might not have been the solution, as the logs only showed warnings. Perhaps the issue was resolved simply by using expo prebuild and building through Xcode.
I still observe an issue related to the new Xcode 15 version when using eas-cli. This is something that Expo or Xcode should address, especially for beginners.
dagdanmo
commented
8 months ago @erdemgonul Probably a dumb question from my part here, but I have also been looking into making sure that the pods are generated with a specific deployment_target. Does it matter where in the Podfile I place it?
Can also confirm that my Xcode Logs said something about deployment_target.
Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'expo-dev-client' from project 'Pods')
warning: Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'project' from project 'project')
note: Run script build phase '[Expo] Configure project' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'project' from project 'project')
warning: Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'project' from project 'project')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'RNScreens' from project 'Pods')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'RNReanimated' from project 'Pods')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'RNGestureHandler' from project 'Pods')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'RNCMaskedView' from project 'Pods')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'RNCAsyncStorage' from project 'Pods')
warning: Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')
phil-hudson
commented
7 months ago anyone have a workaround/solution?
dagdanmo
commented
7 months ago @erdemgonul's trick worked for me, @phil-hudson, with some slight moderations.
My approach to this:
Open projectName.xcworkspace in Xcode and build from there.
Another aproach: delete node modules and ios-folder and run:
App launches from that.
Hope this helps.
ybentz
commented
7 months ago May not be relevant for other people but for me the OP's warnings didn't end up being the build failure culprit but it was really confusing so posting in case it helps anyone.
When I ran the build without cleaning up the build folder (as described above by @szdziedzic) and opened the Xcode logs I saw a few warnings but only one error:
Provisioning profile "*[expo] XXX AdHoc XXX" doesn't include signing certificate "Apple Distribution: XXX". A quick search led me to this issue and deleting my local non-expired certificates as suggested there indeed solved it for me.
guytepper
commented
7 months ago @ybentz that worked for me! thanks a lot for the heads up :)
chenop
commented
7 months ago Got the same error - Here is how I solved it:
react-native run-ios --> Successphil-hudson
commented
7 months ago running the project is working fine for me e.g. npx expo run:ios, however running a prod build command such as:
"eas build --profile production --platform android --local"
is still failing, even after running a prebuild in xcode as the suggestion above states.
Logs:
[RUN_FASTLANE] 2023-12-07 08:34:50.370 xcodebuild[14455:236448] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
[RUN_FASTLANE] Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists.
[RUN_FASTLANE] Function: createItemModels(for:itemModelSource:)
[RUN_FASTLANE] Thread: <_NSMainThread: 0x7fd562f09960>{number = 1, name = main}
[RUN_FASTLANE] Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
[RUN_FASTLANE] ** ARCHIVE FAILED **
[RUN_FASTLANE] Exit status: 65
[RUN_FASTLANE]
[RUN_FASTLANE] +---------------------------------------+
[RUN_FASTLANE] | Build environment |
[RUN_FASTLANE] +-------------+-------------------------+
[RUN_FASTLANE] | xcode_path | /Applications/Xcode.app |
[RUN_FASTLANE] | gym_version | 2.217.0 |
[RUN_FASTLANE] | sdk | iPhoneOS17.0.sdk |
[RUN_FASTLANE] +-------------+-------------------------+
[RUN_FASTLANE] Looks like fastlane ran into a build/archive error with your project
[RUN_FASTLANE] It's hard to tell what's causing the error, so we wrote some guides on how
[RUN_FASTLANE] to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[RUN_FASTLANE] Before submitting an issue on GitHub, please follow the guide above and make
[RUN_FASTLANE] sure your project is set up correctly.
[RUN_FASTLANE] fastlane uses `xcodebuild` commands to generate your binary, you can see the
[RUN_FASTLANE] the full commands printed out in yellow in the above log.
[RUN_FASTLANE] Make sure to inspect the output above, as usually you'll find more error information there
[RUN_FASTLANE]
[RUN_FASTLANE] [!] Error building the application - see the log above
[RUN_FASTLANE] Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
[CLEAN_UP_CREDENTIALS] Destroying keychain - /var/folders/3p/31fp7bl56pd_1y_y4xbf2ltr0000gn/T/turtle-v2-515edfe7-1346-45c7-8e78-1451c0daf94f.keychain
[CLEAN_UP_CREDENTIALS] Removing provisioning profile
trilo01
commented
7 months ago Got the same error - Here is how I solved it:
- Opened xcode --> Build --> Got the error: "No template named 'unary_function' in namespace 'std'; did you mean '__unary_function'?"
- Following Similar SO Question - just clicked "Fix" on the error.
- Build in Xcode --> Success
- ran:
react-native run-ios--> Success
Thanks it worked for me
clausjoergensen
commented
6 months ago FYI, this was caused by a bug in Xcode that was fixed in Xcode 15.1 (rdar://13194758)
However, this thread is very concerning as it was always a warning in xcodebuild. If the warning caused eas-cli to report builds as failed, that's a bug in eas-cli that needs to be fixed.
Lacamoura48
commented
5 months ago I had to run pod install on ./ios and then npm run ios it worked just fine.
SwadhinBaroi
commented
5 months ago I had to run
pod installon./iosand thennpm run iosit worked just fine.
This technique works for me.
Lurtroxx
commented
5 months ago Anyone find a solution to this? I am stuck on multiple projects.
michael-flagship
commented
1 week ago I'm still having this issue
kcoderhtml
commented
5 days ago i just encountered this issue with github actions yesterday; I ran a build with the exact same project and build workflow 2 weeks ago, and it worked fine then.
https://github.com/kcoderhtml/scaffold/actions/runs/9966891643/job/27540075513
EDIT:
I was able to succesfully get the warnings to go away by bumping the xcode version to 15.2 instead of the default github actions version 15.0.1. i used maxim-lobanov/setup-xcode to help me set the version
CoreyJ87
commented
15 hours ago I am also having this issue. Tried changing xcode version to 15.2 and 14.3 and it didnt fix it for me. Not sure what other things I should try. Id rather not have to worry about the ios folder as I told normally keep it in the repo
Build/Submit details page URL
No response
Summary
Having this error:
"Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists."Managed or bare?
expo-dev-client
Environment
Error output
Reproducible demo or steps to reproduce from a blank project
private repo, can provide access