react / react/react-native

Device need connect to run App in debug mode(Android)

Offen
#58,191 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Needs: Attention Needs: Repro Platform: Android
Vorherrschende Sprache
C++
Sterne
127k
Forks
25.3k
Ø Merge
1 T. 23 Std.
Gemergte PRs (30 T.)
4

Beschreibung

Description

Previous version with React Native 0.81.4: Once I installed the app and configured the bundle, I could disconnect the device from the USB cable or wireless connection and still run/debug the app and make code changes. This functionality has completely stopped in the latest React Native 0.87.1 version. Please fix this.

The scenario I am facing is mentioned below.

Upgrade from React Native 0.81.4 to 0.87

Previously, when we installed the debug APK on the phone, Metro would start and the app would connect to Metro automatically. The app could start even without a USB or wireless connection.

After upgrading from React Native 0.81.4 to 0.87, the behavior has changed.

  1. Metro Connection Requirement

After the upgrade:

The app starts only when either USB debugging or wireless debugging is connected.
If neither USB nor wireless debugging is connected, Metro starts, but the app does not start/connect properly.
2. Bundle Configuration Behavior

Previously, when we configured the bundle while USB and wireless connections were not available:

The app would not start immediately after configuring the bundle.
We could kill the app and reopen it.
On reopening, the app would start successfully.
The configured values would be saved and retained.

After upgrading to React Native 0.87:

We configure the bundle, but the app does not start.
We kill the app and reopen it.
The app again asks us to configure the bundle.
After configuring the bundle again, the app still does not start.
The configured values are not being retained as expected.
3. Behavior When USB/Wireless Is Connected

When either USB or wireless debugging is connected:

The app starts successfully.
After killing the app and opening it again, the app starts successfully on the second attempt.
Summary

The main issue after upgrading from React Native 0.81.4 to 0.87 is that the debug APK now appears to depend on an active USB or wireless Metro connection to start correctly. In addition, when Metro is not connected, the configured bundle values are not being retained after restarting the app.

Steps to reproduce
  • create new react-native project with version 0.87.X and check
  • App install and with usb cable
  • now remove usb cable and configure bundler
  • Kill App and open Again
  • it will not open
  • if usb and wireless dissconnected app will not start , it will ask to bundle configure after bundle configure also app not start , kill ask again to bundle configure and repeat same steps again and again
React Native Version

0.87.1

Affected Platforms

Runtime - Android

Output of npx @react-native-community/cli info
latest react-native version and CLI
Stacktrace or Logs
Stuck on first line and no going ahead
MANDATORY Reproducer

https://github.com/sandeepkudalepanvel-commits/SocietyMobileApp

Screenshots and Videos

No response

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit dem obligatorischen Reproducer und vergleiche den Android-Debug-Start in React Native 0.81.4 und 0.87.1, wobei USB- und drahtloses Debugging getrennt sind. Verfolge den im Bericht beschriebenen Metro-Verbindungs- und Bundle-Konfigurationsablauf. Als erledigt gilt die Aufgabe, wenn die Debug-App ohne eine der beiden Verbindungen startet und ihre konfigurierten Bundle-Werte nach dem Beenden und erneuten Öffnen beibehält.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
react-native
Bereich
mobile-dev
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.