react / react/react-native

React Native Bundler Bug?

Open
#49,995 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

📦Bundler Needs: Attention Needs: Repro Stale
Dominant language
C++
Stars
127k
Forks
25.3k
Avg merge
1d 23h
Merged PRs (30d)
4

Description

Description

I'm not sure what's going on. I spent the afternoon trying to figure out how to run a new React Native project at version 0.78.0. I simply created a new project using the following command:

npx @react-native-community/cli@17.0.0 init AwesomeProject --version 0.78.0

The project was created, and I was able to build it successfully. However, as soon as I ran the Metro bundler, the app displayed a black screen. I had to manually close the app and reopen it for anything to appear.

Steps to reproduce
  1. First init a new project with npx @react-native-community/cli@17.0.0 init AwesomeProject --version 0.78.0
  2. Run npm run android && npm run start
  3. Await it to build, as soon as the app run close it, and open again manually.
React Native Version

0.78.0

Output of npx @react-native-community/cli info
System:
  OS: Linux 6.8 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
  CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
  Memory: 11.77 GB / 31.28 GB
  Shell:
    version: 5.2.21
    path: /bin/bash
Binaries:
  Node:
    version: 18.18.0
    path: ~/.nvm/versions/node/v18.18.0/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/bin/yarn
  npm:
    version: 10.8.3
    path: ~/.nvm/versions/node/v18.18.0/bin/npm
  Watchman:
    version: 20231224.093142.0
    path: /usr/local/bin/watchman
SDKs:
  Android SDK:
    API Levels:
      - "26"
      - "27"
      - "28"
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 28.0.3
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 32.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
      - 35.0.0
      - 35.0.1
    System Images:
      - android-26 | Intel x86 Atom
      - android-26 | Intel x86 Atom_64
      - android-26 | Google APIs Intel x86 Atom_64
      - android-27 | Intel x86 Atom
      - android-27 | Intel x86 Atom_64
      - android-28 | Intel x86 Atom
      - android-28 | Intel x86 Atom_64
      - android-28 | Google Play Intel x86 Atom
      - android-28 | Google Play Intel x86 Atom_64
      - android-35 | Google APIs Intel x86_64 Atom
    Android NDK: Not Found
IDEs:
  Android Studio: Not Found
Languages:
  Java:
    version: 11.0.26
    path: /usr/bin/javac
  Ruby:
    version: 3.2.3
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.1
    wanted: 15.0.1
  react:
    installed: 19.0.0
    wanted: 19.0.0
  react-native:
    installed: 0.78.0
    wanted: 0.78.0
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: false
Screenshots and Videos

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by creating React Native 0.78.0 with the stated CLI command, then run npm run android && npm run start on the reported Android environment. Start by tracing the Metro bundler startup path and compare the first launch with reopening the app. Done means a newly built app displays normally on its first launch without manually closing and reopening it.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, javascript, react-native
Domain
build-system, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.