Idb flipper error for real device iOS testing
See original GitHub issue🐛 Bug Report
When I want to debug my real iOS device, I got this message
To Reproduce
brew tap facebook/fb
brew install idb-companion
sudo pip3 install fb-idb
which idb
return /usr/local/bin/idb
Finally idb list-targets
find my device
Environment
Mac OS 10.15.4 Flipper 0.46.0 iPhone 11 pro 13.3.1 React-native 0.62.2
Issue Analytics
- State:
- Created 3 years ago
- Reactions:30
- Comments:14 (4 by maintainers)
Top Results From Across the Web
Troubleshooting iOS Issues - Flipper
Make sure idb is installed and configured in the Flipper settings. iOS simulator device not showing up. Ensure that your simulator is on...
Read more >react-native flipper no devices found issue - Stack Overflow
but Flipper says me NO DEVICES FOUND. I searched all of ways, but I can't fix it. I tried... set correct android SDK...
Read more >Commands - idb
Running commands against a specific iOS Target idb maintains local state of iOS Targets that it is aware of. This state can be...
Read more >How to enroll iOS devices to AstroFarm?
Ensure the value of Command Line Tools: To do this, launch the XCode application on the mac machine and navigate to Preferences under...
Read more >I get "Failed to prepare device fo… | Apple Developer Forums
Restarting my iPhone fixed this right away for me. ... Failed to prepare device for development. ... Recovery Suggestion: If you are certain...
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
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
Please bear with us, we’re still ironing out some issues with physical iOS device support at the moment, in particular, today’s release contains one fix, and there’s another fix in idb on the way that should help.
any updates on this?