CocoaPods 1.15.0 : File exists @ syserr_fail2_in Error - Workaround available
#42698
Comments
|
I'd like to report the same issue with additional info. I've tried:
All yielded the same result. Here is my setup, CommandStackPlugins |
|
same problem here: Installing hermes-engine (0.73.2) [!] Error installing hermes-engine ――― MARKDOWN TEMPLATE ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― CommandReport
StackPluginsPodfile# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', __dir__]).strip
platform :ios, min_ios_version_supported
# prepare_react_native_project!
# Prepare React Native project (if this method is defined in react_native_pods.rb)
prepare_react_native_project! if defined?(prepare_react_native_project!)
# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
# dependencies: {
# ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'HarnessReact' do
config = use_native_modules!
use_react_native!(
:path => config[:reactNativePath],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
:flipper_configuration => flipper_config,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
target 'HarnessReactTests' do
inherit! :complete
# Pods for testing
end
# post_install do |installer|
# # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
# react_native_post_install(
# installer,
# config[:reactNativePath],
# :mac_catalyst_enabled => false
# )
# end
endError |
|
I'm seeing this only happen when using CocoaPods 1.15.0, which was released 7 hours ago. Using CocoaPods 1.14 works without error for me. It appears the stack traces posted here are all using 1.15.0 as well. As a workaround, you could pin the CocoaPods version to the last stable release for 1.14 until it gets resolved for 1.15. Or using brew (brew doesn't have version pinning for cocoapods): |
|
amazing, thank you very much, downgrading to 1.14 solved my problem. gem install cocoapods -v 1.14.3 |
|
Using @allynsweet solution, you can as another workaround, modify the Gemfile and set the CocoaPods version to 1.14 |
|
I had this issue and downgrading cocoapods did work for me too |
|
Same. Downgrading to 1.14 worked for me as well. |
kelset
changed the title
File exists @ syserr_fail2_in Error - Workaround available
|
Someone already opened an issue in the Cocoapods repo: CocoaPods/CocoaPods#12226 The workaround, so far, is to downgrade to Cocoapods 1.14. |
Summary: Users aren't able to build (#42698). We're restricting the version to known good version of Cocoapods until the next release. Changelog: [iOS][Fixed] don't allow cocoapods 1.15.
Summary: Users aren't able to build (#42698). We're restricting the version to known good version of Cocoapods until the next release. Changelog: [iOS][Fixed] don't allow cocoapods 1.15.
) Summary: Cocoapods 1.15 (#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. ## Changelog: [iOS][Fixed] don't allow cocoapods 1.15. <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: #42702 Test Plan: ``` bundle exec pod install ``` Reviewed By: cipolleschi Differential Revision: D53180111 Pulled By: blakef fbshipit-source-id: 4c5dd11db6d208e8d71249443a8f85e601913abd
|
Would you happen to know a quick temporary fix for Expo apps? I've had the same issue with an Expo app since the morning. Cannot build for iOS anymore. I don't know how to change the cocoapod version as reinstalling an older pod with brew has no effect. I deleted node_modules and ios folders. |
) Summary: Cocoapods 1.15 (#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. [iOS][Fixed] don't allow cocoapods 1.15. <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: #42702 Test Plan: ``` bundle exec pod install ``` Reviewed By: cipolleschi Differential Revision: D53180111 Pulled By: blakef fbshipit-source-id: 4c5dd11db6d208e8d71249443a8f85e601913abd
|
Facing the same error after making the new react native project |
) Summary: Cocoapods 1.15 (#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. ## Changelog: [iOS][Fixed] don't allow cocoapods 1.15.
) Summary: Cocoapods 1.15 (#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. [iOS][Fixed] don't allow cocoapods 1.15. <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: #42702 Test Plan: ``` bundle exec pod install ``` Reviewed By: cipolleschi Differential Revision: D53180111 Pulled By: blakef fbshipit-source-id: 4c5dd11db6d208e8d71249443a8f85e601913abd
|
I already tried to downgrade cocopods as @allynsweet mentioned. But it turns out that it still using the 1.15 cocopads, does anyone know how to solve it? pod --version
# 1.14.3error info ...
### Stack
CocoaPods : 1.15.0
Ruby : ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [arm64-darwin23]
RubyGems : 3.5.4
Host : macOS 14.1 (23B2073)
Xcode : 15.2 (15C500b)
Git : git version 2.43.0
Ruby lib dir : /opt/homebrew/Cellar/ruby/3.3.0/lib
Repositories : trunk - CDN - https://cdn.cocoapods.org/
### Plugins
cocoapods-deintegrate : 1.0.5
cocoapods-plugins : 1.0.0
cocoapods-search : 1.0.1
cocoapods-trunk : 1.6.0
cocoapods-try : 1.2.0
... |
|
@Louis-C7 @A320Peter It's hard to be sure without seeing more info, but check your Gemfile in the root of your project, does it say If so, change this to read |
Try - sudo gem uninstall cocoapods |
|
I am new to RN, and I don't have a Gemfile in my project's folder; I am developing with Expo, and it's all handled automatically. I haven't installed cocoapods at all. When I run the command |
|
Upgrading to 1.15.1 did not work for me... I was seeing some build errors like:
But I just upgraded to 1.15.2 on gem, and my app built and is running on device successfully. |
|
Indeed, looks like 1.15.2 has the fix CocoaPods/CocoaPods@f4097d1 |
solved for me as well! |
my MAC is M3 MAX and pod use 1.15.1 always report this...and finally 1.15.2 fixed |
|
Can confirm as well that 1.15.1 was still giving issues, but 1.15.2 fixed it for me as well. |
|
1.15.2 is the answer for me aswell |
|
How do you set the version of Cocoapods in a CI environment like AppCenter? Or simply using RN 0.73.4 installs the latest Cocoapods? I am getting the build to work locally. But still failing in AppCenter? Also I am actually using the latest 0.72.10 version locally and AppCenter. Do I need to upgrade to the 0.73... version to fix or have other minor versions been patched? |
|
@glennweb I had the same problem with AppCenter builds. I solved it by creating a file named 'appcenter-pre-build.sh' in the root project folder. Its contents are like this: |
…_fail2_in The reason for the issue seems to be a bug in cocoapods < 15.2 See facebook/react-native#42698
## Description Because of the bug with Cocoapods, our CIs are failing on the cached dependencies. This issue has been fixed in React Native 0.73.3 already, but this version requires us to update Cocoapods version. This PR updates our example projects to 0.73.4 version (which is the newest at the moment) and updates the version of Cocoapods. You can read more about the problem [here](facebook/react-native#42698). ## Changes - Updated examples that are matching 0.73 version to 0.73.4 - Updated Cocoapods version pattern in Gemfiles ## Checklist - [x] Ensured that CI passes
…_fail2_in The reason for the issue seems to be a bug in cocoapods < 15.2 See facebook/react-native#42698
|
Running # CocoaPods version 1.15.0 has incompatibilities with React Native
# https://github.com/facebook/react-native/issues/42698
# https://github.com/expo/expo/issues/26828
# https://github.com/CocoaPods/CocoaPods/issues/12226
- name: Upgrade CocoaPods to version 1.15.2
run: |
gem uninstall cocoapods -v 1.15.0 --ignore-dependencies
gem install cocoapods -v 1.15.2
- name: Prepare files for xcodebuild command
run: pnpm expo prebuild --platform ios |
|
Closing the issue as Cocoapods 15.2 fixes it. |
…702) Summary: Cocoapods 1.15 (facebook/react-native#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. ## Changelog: [iOS][Fixed] don't allow cocoapods 1.15. <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: facebook/react-native#42702 Test Plan: ``` bundle exec pod install ``` Reviewed By: cipolleschi Differential Revision: D53180111 Pulled By: blakef fbshipit-source-id: 4c5dd11db6d208e8d71249443a8f85e601913abd Original: facebook/react-native@3869ae4
…702) Summary: Cocoapods 1.15 (facebook/react-native#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. ## Changelog: [iOS][Fixed] don't allow cocoapods 1.15. <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: facebook/react-native#42702 Test Plan: ``` bundle exec pod install ``` Reviewed By: cipolleschi Differential Revision: D53180111 Pulled By: blakef fbshipit-source-id: 4c5dd11db6d208e8d71249443a8f85e601913abd Original-Commit: facebook/react-native@3869ae4
…702) Summary: Cocoapods 1.15 (facebook/react-native#42698) current breaks the build, limit to version >= 1.13 & < 1.15 This is currently broken and affecting users, we'll remove this limit once Cocopods fixes the regression. It's currently blocking 0.73.3. ## Changelog: [iOS][Fixed] don't allow cocoapods 1.15. <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests Pull Request resolved: facebook/react-native#42702 Test Plan: ``` bundle exec pod install ``` Reviewed By: cipolleschi Differential Revision: D53180111 Pulled By: blakef fbshipit-source-id: 4c5dd11db6d208e8d71249443a8f85e601913abd Original-Commit: facebook/react-native@3869ae4
|
@cipolleschi Would it make sense to revert or update #42702 | 3869ae4 |
Summary: Previously we had to limit (facebook#42702) Cocoapods to avoid a broken version, this is no longer the case. Changelog: [iOS][Changed] - Remove limit on Cocoapods to allow 1.15.2 Differential Revision: D56299927
Summary: Previously we had to limit (facebook#42702) Cocoapods to avoid a broken version, this is no longer the case. Changelog: [iOS][Changed] - Remove limit on Cocoapods to allow 1.15.2 Differential Revision: D56299927
|
@taylorkline no, I don't think it is worth. The reason is the following:
So, to avoid ruptures in anyone workflows, it is much safer to keep the limitation in place to avoid issues. You can always customise your Gemfile to pin Cocoapods to 1.15.2, if that's what your team prefer! :D |
|
@cipolleschi it doesn't affect your other points but re:
In the Gemfile? I think there is, I believe you can do the following: gem 'cocoapods', '~> 1.13', '!= 1.15.0', '!= 1.15.1' |
|
@liamjones uh, interesting! #TIL In that case, this is worth doing! cc. @blakef |
and others
Description
This is brand new install following the RN development guide. The error code is not giving a lot of context even with verbose flag.
Steps to reproduce
cd iosbundle installbundle exec pod install --verboseReact Native Version
0.73.2
Affected Platforms
Build - MacOS
Output of
npx react-native infoStacktrace or Logs
Stack
Plugins
Podfile
Error
Reproducer
https://github.com/nikodraca/fitcheq
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: