Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
#58,191 2 comentários 1 reação 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
42/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
react-native
Domínio
mobile-dev

Direção de pesquisa

Comece com o reprodutor obrigatório e compare a inicialização de depuração do Android no React Native 0.81.4 e 0.87.1, com a depuração USB e sem fio desconectada. Rastreie o fluxo de conexão do Metro e de configuração do bundle descrito no relatório. Está concluído quando o aplicativo de depuração inicia sem nenhuma das duas conexões e mantém seus valores de bundle configurados depois de ser encerrado e reaberto.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Needs: Attention Needs: Repro Platform: Android
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

Linguagem predominante
C++
Estrelas
127k
Forks
25.3k
Métricas de merge de PRs
Nenhum PR com merge em 30d

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de react/react-native

Todas as issues de react/react-native

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.