Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[0.63-rc.0] [Android] Could not find Native Module for JSDevSupport #28746

Closed
jerameel opened this issue Apr 24, 2020 · 11 comments
Closed

[0.63-rc.0] [Android] Could not find Native Module for JSDevSupport #28746

jerameel opened this issue Apr 24, 2020 · 11 comments
Labels
Needs: Triage 🔍 Platform: Android Android applications. Resolution: Locked This issue was locked by the bot.

Comments

@jerameel
Copy link

Description

Enabling debug mode on android for a new project shows the following error. See screenshot below.

React Native version:

System:
OS: macOS 10.15.3
CPU: (12) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
Memory: 158.79 MB / 16.00 GB
Shell: 5.0.11 - /usr/local/bin/bash
Binaries:
Node: 13.0.1
npm: 6.12.0
Watchman: 4.9.0
SDK:
Android SDK:
API Levels: 23, 25, 26, 27, 28, 29
Build Tools: 28.0.3, 29.0.2, 29.0.3
Languages:
Java: 1.8.0_222
Python: 2.7.16
npmPackages:
react: 16.13.1 => 16.13.1
react-native: 0.63.0-rc.0 => 0.63.0-rc.0

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

  1. npx react-native init RN063 --version 0.63.0-rc.0
    2.react-native start and react-native run-android
  2. Enable debug mode on react native dev menu.

Expected Results

Should work the same as debug mode disabled

Screenshot_1587742830

@acuariol
Copy link

report

@cryptedx
Copy link

cryptedx commented May 1, 2020

I am having the same problem with my app. iOS fine. Android with debugging enabled is not working.

@lylysunshinee
Copy link

I am having the same problem with android app in debug mode. IOS fine

@kesha-antonov
Copy link
Contributor

Same here

@emadhajjar
Copy link

Same here on Android when running debug and it work normally when stop debugging

@RobTheFiveNine
Copy link

Same here on Android when running debug and it work normally when stop debugging

Same scenario here

@tuanpi
Copy link

tuanpi commented May 28, 2020

Similarly when running on real devices

@BrunoVillanova
Copy link
Contributor

Same here.

@alexwasner
Copy link

I was getting a white screen upon upgrading. Attempted to toggle debugger and discovered this as well.

@BrunoVillanova
Copy link
Contributor

Are some of you using wix RNN?

@jreason
Copy link

jreason commented May 29, 2020

@BrunoVillanova no we are using @react-navigation

grabbou pushed a commit that referenced this issue Jul 7, 2020
Summary:
Currently on react native 0.63-rc.0 and 0.63-rc.1 enabling debugging throws an exception. It looks like something may have been missed in unregistering JSDevSupport in this commit c20963e

![crash](https://user-images.githubusercontent.com/14797029/85500252-2acae400-b5b1-11ea-938a-674b55e649b2.gif)

This should fix #28746 and #29136

## Changelog
[Android] [Fixed] - Fix crash when enabling debug

Pull Request resolved: #29204

Test Plan:
To recreate the bug:

npx react-native init RN063 --version 0.63.0-rc.1
react-native start
react-native run-android
Enable debug mode from react native dev menu

After this commit, the crash no longer occurs

![non crash](https://user-images.githubusercontent.com/14797029/85500241-269ec680-b5b1-11ea-8cfe-85bfda4dd222.gif)

Reviewed By: TheSavior

Differential Revision: D22395406

Pulled By: RSNara

fbshipit-source-id: 046df77ae1c1de96870fb46f409d59e7d6a68c0d
@facebook facebook locked as resolved and limited conversation to collaborators Oct 1, 2021
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Oct 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Needs: Triage 🔍 Platform: Android Android applications. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

Successfully merging a pull request may close this issue.