Skip to content

Regression from PR #47458: Cannot install React Native from Git anymore #50460

Open

Description

@MicroDroid

Description

This PR updates shouldSkipGenerationForRncore as such it checks if .../ReactCommon exists before deciding to skip rncore generation, whereas previously it would check .../ReactCommon/react/renderer/components/rncore specifically.

This change breaks installations from Git.

I noticed this while upgrading from 0.76.2 to 0.78.1.

Per my debugging:

  • Previous behavior:
    • When installing from NPM: rncore is pre-generated using the prepack script
    • When installing from Git: rncore gets generated when running pod install
  • Current behavior:
    • When installing from NPM: rncore is pre-generated using the prepack script
    • When installing from Git: rncore will NOT get generated when running pod install because .../ReactCommon is detected as exists even though .../ReactCommon/react/renderer/components/rncore does not

Steps to reproduce

npx @react-native-community/cli@latest init BuggyReactNative
cd ./BuggyReactNative/
npm install 'https://gitpkg.vercel.app/facebook/react-native/packages/react-native?0.78-stable'
cd ./ios/
bundle exec pod install
cd ..
ls ./node_modules/react-native/ReactCommon/react/renderer/components/rncore
# 💥 no such file or directory
# 💥 Xcode won't build the project

React Native Version

0.78.1

Affected Platforms

Runtime - iOS, Other (please specify)

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

Not relevant

Stacktrace or Logs

Not relevant

Reproducer

Run the reproducer bash script so you can test with your toolchain not mine

Screenshots and Videos

No response

Activity

  1. react-native-bot commented on Apr 3, 2025

    @react-native-bot
    Collaborator

    Warning

    Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2.

  2. added
    Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.
    Impact: RegressionDescribes a behavior that used to work on a prior release, but stopped working recently.
    and removed on Apr 3, 2025
  3. react-native-bot commented on Apr 3, 2025

    @react-native-bot
    Collaborator

    Warning

    Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2.

  4. react-native-bot commented on Apr 3, 2025

    @react-native-bot
    Collaborator

    Warning

    Missing reproducer: We could not detect a reproducible example in your issue report. Please provide either:

  5. react-native-bot commented on Apr 28, 2025

    @react-native-bot
    Collaborator

    This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.

  6. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    and removed
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Apr 28, 2025
  7. MicroDroid commented on Apr 28, 2025

    @MicroDroid
    Author

    @react-native-bot the info is all there

  8. react-native-bot commented on Oct 26, 2025

    @react-native-bot
    Collaborator

    This issue is stale because it has been open for 180 days with no activity. It will be closed in 7 days unless you comment on it or remove the "Stale" label.

  9. react-native-bot commented on Oct 26, 2025

    @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.

  10. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Oct 26, 2025
  11. MicroDroid commented on Oct 26, 2025

    @MicroDroid
    Author

    .

  12. removed
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Oct 26, 2025
  13. react-native-bot commented on Apr 24, 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.

  14. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Apr 24, 2026
  15. MicroDroid commented on Apr 24, 2026

    @MicroDroid
    Author

    .

  16. removed
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Apr 25, 2026
  17. react-native-bot commented on Oct 22, 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.

  18. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Oct 22, 2026
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

    Impact: RegressionDescribes a behavior that used to work on a prior release, but stopped working recently.Needs: AttentionIssues where the author has responded to feedback.Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.Needs: Version InfoStaleThere 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