local iOS build failing with "Details: createItemModels creation requirements should not create capability item model" #2111
Comments
|
Same issue here! It was working totally fine yesterday |
|
Same here |
|
same here |
|
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 |
|
I am also facing same issue after upadating xcode version to 15.0 |
|
FIx that worked for me:
|
|
Same issue here, any workaround? The above one didn't help. |
Same issue here, and I decide to downgrade my Xcode into 14.3.1 |
|
Hi, Does this issue only occur for you when running builds with the 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 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. 
|
|
Unfortunately, I wasn't able to replicate the issue on my test app both locally and on the EAS server. |
|
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 |
|
Ok, so I was able to get the same warning in the |
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 In 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 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. |
|
@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. |
|
anyone have a workaround/solution? |
|
@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:
App launches from that. Hope this helps. |
|
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: |
|
@ybentz that worked for me! thanks a lot for the heads up :) |
|
Got the same error - Here is how I solved it:
|
|
running the project is working fine for me e.g. "eas build --profile production --platform android --local" is still failing, even after running a prebuild in xcode as the suggestion above states. Logs: |
Thanks it worked for me |
|
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 |
|
I had to run |
This technique works for me. |
|
Anyone find a solution to this? I am stuck on multiple projects. |
|
I'm still having this issue |
|
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 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 |
and others
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
expo-env-info 1.0.5 environment info: System: OS: macOS 14.0 Shell: 5.9 - /bin/zsh Binaries: Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node Yarn: 1.22.19 - ~/.nvm/versions/node/v18.14.2/bin/yarn npm: 9.8.1 - ~/.nvm/versions/node/v18.14.2/bin/npm Watchman: 2023.10.30.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.11.2 - /Users/albertgao/.rbenv/shims/pod SDKs: iOS SDK: Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0 Android SDK: API Levels: 30, 31 Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0 System Images: android-30 | ARM 64 v8a, android-31 | Google APIs ARM 64 v8a IDEs: Xcode: 15.0.1/15A507 - /usr/bin/xcodebuild npmPackages: expo: 49.0.16 => 49.0.16 metro: 0.76.8 => 0.76.8 react: 18.2.0 => 18.2.0 react-dom: ^18.2.0 => 18.2.0 react-native: 0.72.6 => 0.72.6 react-native-web: ~0.19.7 => 0.19.9 npmGlobalPackages: eas-cli: 5.6.0 Expo Workflow: managedError output
Reproducible demo or steps to reproduce from a blank project
private repo, can provide access
The text was updated successfully, but these errors were encountered: