No route to flipper found when wifi debugging
See original GitHub issue🐛 Bug Report
Getting " no route to flipper found" when connected using wifi debugging. can’t connect db plugin
To Reproduce
- Use any android device.
- Add flipper db plugin
client.addPlugin(new DatabasesFlipperPlugin(this));
- connect the device using
adb connect IP:PORT
- install the app
Environment
Devices
- Android 7.1.1 (Samsung Galaxy TAB A)
- Android 7.1.2 (ELO TAB)
Implementations
debugImplementation 'com.facebook.flipper:flipper:0.31.2'
debugImplementation 'com.facebook.soloader:soloader:0.8.2'
Flipper desktop version : 0.31.2 (Ubuntu 18.4)
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Wifi Dev Module issues - Flipper Zero Forum
Hello, I would like to point out a few issues with the Dev Modules. This documentation (and following pages) is obsolete as of...
Read more >Debugging React Native apps with Flipper - LogRocket Blog
Learn how to debug your React Native app using Flipper, one of the best and simplest debuggers available today.
Read more >Wi-Fi Debug (ADB) - There was an error pairing the device
In your smartphone (Go to Settings->Developer options-> Wireless Debugging->Pair device with pairing code). Copy the ipaddress & port. For ...
Read more >Debugging - Expo Documentation
Learn about different techniques and tools available to debug your Expo project.
Read more >React Native Flipper: A Better Way of Debugging - Pagepro
It's an open-source debugging tool made by Facebook for mobile apps – both iOS and Android. It existed for quite some time, but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just tried it locally, and it seems to works fine for me if I:
adb devices
shows devicesadb tcpip 5555
adb connect <phone ip>:5555
Please do make sure the ports 5555, 5037, 8088, 8089 are open and no other process is running on them (especially the last two are quite common)
Working on v0.136.0 and the new wireless debugging feature by Android Studio Bumblebee