0.72: Remote debugging broken on Android #38006

edstbbz · 2023-06-21T20:29:58Z

Description

When upgrading to 0.72, the application crashes when connected to the Chrome debugger (test on Android)

2023-06-22 00:19:01.199 22414-22948 libc 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.750 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG 2023-06-22 00:19:01.751 22956-22956 DEBUG com.myapp.releasestaging A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 22948 (mqt_js), pid 22414 (.releasestaging)
pid-22956 A Cmdline: com.myapp.releasestaging
pid-22956 A pid: 22414, tid: 22948, name: mqt_js >>> com.myapp.releasestaging <<<
pid-22956 A #00 pc 000000000003b7f4 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreact_render_runtimescheduler.so (facebook::react::RuntimeSchedulerBinding::createAndInstallIfNeeded(facebook::jsi::Runtime&, std::__ndk1::shared_ptrfacebook::react::RuntimeScheduler const&)+68) (BuildId: 154f261ff589aa1e)
pid-22956 A #1 pc 00000000002055e1 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #2 pc 0000000000205591 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #3 pc 0000000000205531 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #4 pc 00000000002054e1 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #5 pc 0000000000204300 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #6 pc 000000000028b3a9 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #7 pc 000000000028ad2c /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (std::__ndk1::function<void (facebook::jsi::Runtime&)>::operator()(facebook::jsi::Runtime&) const+44) (BuildId: eedf0b28937d60c0)
pid-22956 A #8 pc 000000000028ac68 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #9 pc 000000000028ac11 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #10 pc 000000000028abb1 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #11 pc 000000000028ab61 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #12 pc 0000000000289ab0 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #13 pc 00000000002b56b9 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #14 pc 00000000002b5629 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (std::__ndk1::function<void (facebook::react::JSExecutor*)>::operator()(facebook::react::JSExecutor*) const+57) (BuildId: eedf0b28937d60c0)
pid-22956 A #15 pc 00000000002b55e6 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #16 pc 00000000002b556c /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #17 pc 00000000002b551c /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #18 pc 00000000002b54ec /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #19 pc 00000000002b43b8 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #20 pc 00000000003e56d1 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libhermes_executor.so (BuildId: 53166c965b19a311)
pid-22956 A #21 pc 00000000003e5694 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libhermes_executor.so (std::__ndk1::function<void ()>::operator()() const+20) (BuildId: 53166c965b19a311)
pid-22956 A #22 pc 00000000002153c4 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #23 pc 000000000021533c /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #24 pc 00000000002152ec /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #25 pc 00000000002152bc /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #26 pc 0000000000214248 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libreactnativejni.so (BuildId: eedf0b28937d60c0)
pid-22956 A #27 pc 0000000000016979 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libfbjni.so (facebook::jni::detail::MethodWrapper<void (facebook::jni::JNativeRunnable::)(), &(facebook::jni::JNativeRunnable::run()), facebook::jni::JNativeRunnable, void>::dispatch(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject>)+25) (BuildId: 24c51b71e72aa958d98c6f3c2304d6447e26c99e)
pid-22956 A #28 pc 00000000000168f4 /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/lib/x86_64/libfbjni.so (facebook::jni::detail::FunctionWrapper<void ()(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject>), facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject*, void>::call(_JNIEnv*, _jobject*, void ()(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject>))+52) (BuildId: 24c51b71e72aa958d98c6f3c2304d6447e26c99e)
pid-22956 A #37 pc 00000000003ea1f2 [anon:dalvik-classes.dex extracted in memory from /data/app/~~4hmgMGlidXP0t4CIdUV4PA==/com.myapp.releasestaging-ZdypyK0mTp6SdihqT5qtnA==/base.apk] (com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run+74)

React Native Version

0.72.0

Output of `npx react-native info`

System:
OS: macOS 12.6.1
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 38.58 MB / 16.00 GB
Shell:
version: 5.8.1
path: /bin/zsh
Binaries:
Node:
version: 16.13.0
path: /usr/local/bin/node
Yarn:
version: 3.2.1
path: /usr/local/bin/yarn
npm:
version: 8.1.0
path: /usr/local/bin/npm
Watchman:
version: 2022.10.24.00
path: /usr/local/bin/watchman
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms:
- DriverKit 21.4
- iOS 16.0
- macOS 12.3
- tvOS 16.0
- watchOS 9.0
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9514443
Xcode:
version: 14.0.1/14A400
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.11
path: /usr/bin/javac
Ruby:
version: 2.6.5
path: /Users/user/.rvm/rubies/ruby-2.6.5/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.0
wanted: 0.72.0
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: false
newArchEnabled: false

Steps to reproduce

react-native-run-android
connect to Chrome debugger

Snack, code example, screenshot, or link to a repository

The text was updated successfully, but these errors were encountered:

github-actions · 2023-06-21T20:30:13Z

⚠️	Add or Reformat Version Info
ℹ️	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.70.2

lunaleaps · 2023-06-21T22:52:31Z

Was able to reproduce this with a new app. See stacktrace: https://gist.github.com/lunaleaps/b6dafc94fbe22017e2737b15831ec0ad

lunaleaps · 2023-06-22T03:26:40Z

As well, with iOS I get this error:

info Opening flipper://null/Hermesdebuggerrn?device=React%20Native...
error Browser exited with error:, invalid url, missing http/https protocol
info Opening flipper://null/Hermesdebuggerrn?device=React%20Native...
error Browser exited with error:, invalid url, missing http/https protocol

cipolleschi · 2023-06-22T08:51:15Z

cc. @huntie as you are working on this part

blakef · 2023-06-22T10:05:19Z

I think this is unrelated, that looks like you don't have the flipper client installed (which should register to handle the flipper url scheme.

As well, with iOS I get this error:

info Opening flipper://null/Hermesdebuggerrn?device=React%20Native...
error Browser exited with error:, invalid url, missing http/https protocol
info Opening flipper://null/Hermesdebuggerrn?device=React%20Native...
error Browser exited with error:, invalid url, missing http/https protocol

huntie · 2023-06-22T11:09:37Z

Hi @edstbbz! Sorry you're encountering this issue. Can you share a little more info on which debugging method you're attempting to launch here? ⬇️

connect to Chrome debugger

As @lunaleaps and @blakef have noted, the current "Open Debugger" flow in the Dev Menu requires a local installation of the Flipper desktop app, and we unfortunately have an unclear error message when this URL cannot be handled 😔.

Likely workarounds:

Install Flipper: https://fbflipper.com/docs/getting-started/
Recommended: As a workaround, our recommended debugging flow (right now) if you're using Hermes is via the manual Chrome DevTools connection flow. This will enable direct (connected to the JS engine on device) debugging via Hermes and Chrome DevTools.

kudnayce · 2023-06-22T11:10:00Z

debugging on android does not work the same error!

edstbbz · 2023-06-22T11:29:56Z

Hi @edstbbz! Sorry you're encountering this issue. Can you share a little more info on which debugging method you're attempting to launch here? ⬇️

connect to Chrome debugger

As @lunaleaps and @blakef have noted, the current "Open Debugger" flow in the Dev Menu requires a local installation of the Flipper desktop app, and we unfortunately have an unclear error message when this URL cannot be handled 😔.

Likely workarounds:

Install Flipper: https://fbflipper.com/docs/getting-started/

Recommended: As a workaround, our recommended debugging flow (right now) if you're using Hermes is via the manual Chrome DevTools connection flow. This will enable direct (connected to the JS engine on device) debugging via Hermes and Chrome DevTools.

Hello, @huntie ! The problem occurs when connecting to http://localhost:8081/debugger-ui or https://github.com/jhen0409/react-native-debugger , when I connect to it, app crashes. Launch via the developer menu in the modal window

edstbbz · 2023-06-22T11:35:03Z

The connection to the flipper worked, but the logs in hermes were not shown, perhaps because there is an old client, since we use Chrome for debugging

AshlandWest · 2023-06-27T22:25:29Z

I am also experiencing this issue, on a clean install of React Native 0.72.0.

My steps to reproduce:

npx react-native init <myProjectsName>
yarn start
a

Errors and Symptoms

The app loaded the example page, then I shook the device and started the debugger. The app crashed immediately and since then has crashed on launch.
In my zsh terminal, the last printed line is: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.<myAppsName>/.MainActivity }
In Logcat on Android Studio, it fails on the error: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 17160 (mqt_js), pid 17088 (com.<myAppsName>)

From my research, it looks like the phone's OS may be killing the application due to the application attempting to access something in memory it shouldn't be.

I get two errors inside the debugger:

DevTools failed to load SourceMap: Could not parse content for file:///Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js.map: Unexpected end of JSON input
DevTools failed to load SourceMap: Could not parse content for file:///importFile.worker.worker.js.map: Unexpected end of JSON input

Regarding your suggestions

Install Flipper
- Flipper is already installed
- I ran brew upgrade to check if there was a version issue somewhere. The problem stayed the same.
Use Hermes via manual Chrome DevTools connection flow.
- These steps didn't work for me. I am running Metro on port 8081 and when adding that to the discovery settings, it doesn't see Hermes React Native.

System info

Phone

Samsung Galaxy S22 Ultra
Android Version: 13
Security Patch Level: June 1, 2023

Computer:

MacBook Pro, 2023
Chip: Apple M2 Max
macOS: 13.2.1

React Native Info

System:
OS: macOS 13.2.1
CPU: (12) arm64 Apple M2 Max
Memory: 2.52 GB / 32.00 GB
Shell:
version: 5.8.1
path: /bin/zsh
Binaries:
Node:
version: 18.14.0
path: ~/.nvm/versions/node/v18.14.0/bin/node
Yarn:
version: 1.22.19
path: ~/.yarn/bin/yarn
npm:
version: 9.3.1
path: ~/.nvm/versions/node/v18.14.0/bin/npm
Watchman:
version: 2023.06.26.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.11.3
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Android SDK:
API Levels:
- "29"
- "30"
- "31"
- "32"
- "33"
Build Tools:
- 29.0.2
- 30.0.2
- 30.0.3
- 31.0.0
- 32.0.0
- 32.1.0
- 33.0.0
System Images:
- android-30 | ARM 64 v8a
- android-30 | Intel x86 Atom_64
- android-30 | Google APIs ARM 64 v8a
- android-30 | Google APIs Intel x86 Atom
- android-30 | Google Play ARM 64 v8a
- android-31 | Google APIs ARM 64 v8a
- android-32 | Google APIs ARM 64 v8a
- android-33 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.9971841
Xcode:
version: 14.3.1/14E300c
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.19
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.0
wanted: 0.72.0
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false

pipo151086 · 2023-06-28T16:11:06Z

hi....

same here....

Chrome Dev Tools and Flipper

BOTH DOESNT WORK....

Hermes debugger does not connect, console is allways empty and breakpoints doest work either>

Flipper V 190
RN 0.72

danisOktaxi · 2023-06-28T20:24:04Z

Hi, same error
with RN 0.72.0
Flipper: 0.182.0

Error log crash on Flipper desktop app:

Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 10277 (mqt_js), pid 10191 (AppName.debug)
Unknown

lunaleaps · 2023-06-28T23:20:10Z

Hey folks, thanks for the continued reports.

We are working on a fix for the remote debugging (when you use the dev menu -> debug option) for 0.72.

We've also found an issue with direct debugging on Android (when you debug like this and are actively investigating. Direct debugging is only available for Hermes (which should be enabled by default for 0.72).

Direct debugging on iOS for 0.72 is functional, it seems to be an Android-only issue

lunaleaps · 2023-07-05T19:27:27Z

Issue is fixed for Android, remote debugging: 0fe5ffd

Pick request for 72: reactwg/react-native-releases#76 (comment)

I've opened a new issue just for direct debugging: #38204

edstbbz added the Needs: Triage 🔍 label Jun 21, 2023

github-actions bot added the Needs: Version Info label Jun 21, 2023

github-actions bot added Needs: Author Feedback and removed Needs: Triage 🔍 labels Jun 21, 2023

lunaleaps added Impact: Regression Describes a behavior that used to work on a prior release, but stopped working recently. 0.72 and removed Needs: Version Info Needs: Author Feedback labels Jun 21, 2023

kelset added Platform: iOS iOS applications. Platform: Android Android applications. Debugger Issues related to React Native DevTools or legacy JavaScript/Hermes debugging labels Jun 22, 2023

mikehardy mentioned this issue Jun 29, 2023

build(deps): react-native 0.72 invertase/react-native-firebase#7210

Merged

8 tasks

lunaleaps changed the title ~~0.72: The application crashes if you connect to Chrome debugger~~ 0.72: Remote debugging broken on Android Jul 5, 2023

lunaleaps closed this as completed Jul 5, 2023

lunaleaps mentioned this issue Jul 5, 2023

fix: Add flipper protocol support react-native-community/cli#2003

Merged

2 tasks

AshlandWest referenced this issue in Salt-PepperEngineering/react-native-nordic-dfu Jul 7, 2023

Add back mtu and retries capabilities for android

4ffc30e

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

0.72: Remote debugging broken on Android #38006

0.72: Remote debugging broken on Android #38006

edstbbz commented Jun 21, 2023 •

edited

Loading

github-actions bot commented Jun 21, 2023

lunaleaps commented Jun 21, 2023

lunaleaps commented Jun 22, 2023

cipolleschi commented Jun 22, 2023

blakef commented Jun 22, 2023

huntie commented Jun 22, 2023 •

edited

Loading

kudnayce commented Jun 22, 2023

edstbbz commented Jun 22, 2023 •

edited

Loading

edstbbz commented Jun 22, 2023

AshlandWest commented Jun 27, 2023 •

edited

Loading

pipo151086 commented Jun 28, 2023

danisOktaxi commented Jun 28, 2023

lunaleaps commented Jun 28, 2023 •

edited

Loading

lunaleaps commented Jul 5, 2023 •

edited

Loading

0.72: Remote debugging broken on Android #38006

0.72: Remote debugging broken on Android #38006

Comments

edstbbz commented Jun 21, 2023 • edited Loading

Description

React Native Version

Output of npx react-native info

Steps to reproduce

Snack, code example, screenshot, or link to a repository

github-actions bot commented Jun 21, 2023

lunaleaps commented Jun 21, 2023

lunaleaps commented Jun 22, 2023

cipolleschi commented Jun 22, 2023

blakef commented Jun 22, 2023

huntie commented Jun 22, 2023 • edited Loading

kudnayce commented Jun 22, 2023

edstbbz commented Jun 22, 2023 • edited Loading

edstbbz commented Jun 22, 2023

AshlandWest commented Jun 27, 2023 • edited Loading

My steps to reproduce:

Errors and Symptoms

Regarding your suggestions

System info

Phone

Computer:

React Native Info

pipo151086 commented Jun 28, 2023

danisOktaxi commented Jun 28, 2023

lunaleaps commented Jun 28, 2023 • edited Loading

lunaleaps commented Jul 5, 2023 • edited Loading

edstbbz commented Jun 21, 2023 •

edited

Loading

Output of `npx react-native info`

huntie commented Jun 22, 2023 •

edited

Loading

edstbbz commented Jun 22, 2023 •

edited

Loading

AshlandWest commented Jun 27, 2023 •

edited

Loading

lunaleaps commented Jun 28, 2023 •

edited

Loading

lunaleaps commented Jul 5, 2023 •

edited

Loading