You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
React Native 0.82.1 - Auto installs Cocoapods #54553
Note: English is not my first language, so I apologize if I misunderstood the original problem.
I'm encountering issues with the pod installation process and finding the CLI behavior confusing. Here are my concerns:
1. Deprecated pod install command
When I run pod install directly, the CLI warns me that it's deprecated and suggests I should use yarn ios instead. However, this creates confusion about the expected workflow.
2. Unclear CLI process
When running yarn ios, I cannot determine whether pods are being installed automatically:
yarn ios
info Found Xcode workspace "goat.xcworkspace"
info No booted devices or simulators found. Launching first available simulator...
info Launching iPhone 17 (iOS 26.1)
Expected behavior:
The CLI should automatically install pods before attempting to build the app (currently it doesn't seem to)
The CLI should provide clear feedback about what's happening during the process (e.g., "Installing pods...", "Pods installed successfully")
3. Using prebuilt RNCore
I'm currently using the prebuilt configuration with a custom script in my package.json:
"pod": "cd ios && RCT_USE_RN_DEP=1 RCT_USE_PREBUILT_RNCORE=1 pod install"
If the CLI is supposed to run pod install automatically, how can I ensure it uses the prebuilt configuration?
How do I know if pods were installed successfully when running yarn ios?
What is the recommended workflow for using prebuilt with the current CLI?
Hey @sreekanthSubramani! The problem you are seeing with Cocoapods is something you should report to the CLI repository. That's component is the one that orchestrate the npm run ios command.
As a workaround, what happens if you do the following:
# from the root of your project:
cd ios
bundle install
bundle exec pod install
??
This installs cocoapods manually in the project.
Then, you can open your project with:
open <ProjectName>.xcworkspace
And build and run from Xcode
Regarding:
Firebase + Google Sign-In + RN 0.82 + NewArch = NOT YET SUPPORTED.
Everyone using this combo must disable New Architecture.
is it true - when i use the new arch and use with firebase google sigin in option ?
the android fails ?
This is not true. As far as we know, Firebase works with the New Architecture. What is not working with Firebase is using the iOS precompiled binaries, which are still experimental, and we are investigating why.
with same specs, installing cocoapods 1.16.2 and making sure in gemfile you have no limit for xcodeproj and adding
gem 'nkf'
at the end of the gemfile. Here is gem file that fixed my cocoapods install error:
Just for reference - you can disable the automatic pod install if your workflow already do that beforehand (like our case) by modifying the react-native.config.js at the root of your project:
Activity
sreekanthSubramani commentedon Nov 16, 2025
Firebase + Google Sign-In + RN 0.82 + NewArch = NOT YET SUPPORTED.
Everyone using this combo must disable New Architecture.
is it true - when i use the new arch and use with firebase google sigin in option ?
the android fails ?
Pnlvfx commentedon Nov 16, 2025
Note: English is not my first language, so I apologize if I misunderstood the original problem.
I'm encountering issues with the pod installation process and finding the CLI behavior confusing. Here are my concerns:
1. Deprecated
pod installcommandWhen I run
pod installdirectly, the CLI warns me that it's deprecated and suggests I should useyarn iosinstead. However, this creates confusion about the expected workflow.2. Unclear CLI process
When running
yarn ios, I cannot determine whether pods are being installed automatically:Expected behavior:
3. Using prebuilt RNCore
I'm currently using the prebuilt configuration with a custom script in my
package.json:pod installautomatically, how can I ensure it uses the prebuilt configuration?yarn ios?cipolleschi commentedon Nov 17, 2025
Hey @sreekanthSubramani! The problem you are seeing with Cocoapods is something you should report to the CLI repository. That's component is the one that orchestrate the
npm run ioscommand.As a workaround, what happens if you do the following:
??
This installs cocoapods manually in the project.
Then, you can open your project with:
And build and run from Xcode
Regarding:
This is not true. As far as we know, Firebase works with the New Architecture. What is not working with Firebase is using the iOS precompiled binaries, which are still experimental, and we are investigating why.
Jasper-creator commentedon Jan 24, 2026
with same specs, installing cocoapods 1.16.2 and making sure in gemfile you have no limit for xcodeproj and adding
gem 'nkf'
at the end of the gemfile. Here is gem file that fixed my cocoapods install error:
// gemfile
source 'https://rubygems.org'
ruby ">= 2.6.10"
gem 'cocoapods', '1.16.2'
gem 'activesupport', '>= 6.1.7.5', '!= 7.1.0'
gem 'xcodeproj'
gem 'concurrent-ruby', '< 1.3.4'
gem 'bigdecimal'
gem 'logger'
gem 'benchmark'
gem 'mutex_m'
gem 'nkf'
vladimirivanoviliev commentedon Jan 29, 2026
Just for reference - you can disable the automatic pod install if your workflow already do that beforehand (like our case) by modifying the
react-native.config.jsat the root of your project:Also I can confirm that Firebase is fully supported on the New Architecture.
react-native-bot commentedon Jul 30, 2026
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
react-native-bot commentedon Aug 6, 2026
This issue was closed because it has been stalled for 7 days with no activity.