Skip to content

React Native 0.82.1 - Auto installs Cocoapods #54553

Closed as not planned
Closed as not planned

Description

@sreekanthSubramani

Description

This is to bring into the concern that whenever the pod install has been done manually,
and cd ../

when i do npx react-native run-ios,
I see the Cocoapods is installing first and the build gets failed.

since, we already install the pods,
and run the ios "npm run ios"
it again triggers the Cocoapods installation and fails.

Steps to reproduce

take any version of 0.82.1v and do npx react-native run-ios

React Native Version

0.82.1

Affected Platforms

Runtime - iOS

Output of npx @react-native-community/cli info

sreekanthsubramani@Sreekanths-MacBook-Air openapinasa % npm run ios

> openapinasa@0.0.1 ios
> react-native run-ios

✖ Installing CocoaPods...
error Something went wrong while installing CocoaPods. Please run pod install manually.
sreekanthsubramani@Sreekanths-MacBook-Air openapinasa %

Stacktrace or Logs

sreekanthsubramani@Sreekanths-MacBook-Air openapinasa % npm run ios

> openapinasa@0.0.1 ios
> react-native run-ios

✖ Installing CocoaPods...
error Something went wrong while installing CocoaPods. Please run pod install manually.
sreekanthsubramani@Sreekanths-MacBook-Air openapinasa %

MANDATORY Reproducer

https://github.com/sreekanthSubramani/for-meta-ReactNative

Screenshots and Videos

If there are any possible workarounds which I did not follow, please excuse and let me know about it,
thanks.

Activity

  1. sreekanthSubramani commented on Nov 16, 2025

    @sreekanthSubramani
    Author

    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 ?

  2. Pnlvfx commented on Nov 16, 2025

    @Pnlvfx

    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?
  3. cipolleschi commented on Nov 17, 2025

    @cipolleschi
    Contributor

    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.

  4. Jasper-creator commented on Jan 24, 2026

    @Jasper-creator

    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'

  5. vladimirivanoviliev commented on Jan 29, 2026

    @vladimirivanoviliev
    Contributor

    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:

    // react-native.config.js
    module.exports = {
      project: {
        ios: {
          automaticPodsInstallation: false,
        },
      },
    };
    

    Also I can confirm that Firebase is fully supported on the New Architecture.

  6. react-native-bot commented on Jul 30, 2026

    @react-native-bot
    Collaborator

    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.

  7. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Jul 30, 2026
  8. react-native-bot commented on Aug 6, 2026

    @react-native-bot
    Collaborator

    This issue was closed because it has been stalled for 7 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Triage 🔍StaleThere has been a lack of activity on this issue and it may be closed soon.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions