question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to find device error on Flipper 0.133.1

See original GitHub issue

🐛 Bug Report

As soon as I open the Flipper, I get Connection failed error.

Failed to find device ‘7F017CFA-5EAB-4285-8AED-77E14A717BCE’ while trying to connect app ‘MyApp’

Everything works fine on the Android emulator but not in the iOS simulator

To Reproduce

  • Start the iOS simulator
  • Open the Flipper App

Environment

  • macOS Monterey 12.0.1
  • Simulator: iPhone 13 - iOS 15.0
  • Flipper Version: 0.133.1
  • React Native: 0.67.2

Flipper logs

Failed to find device ‘7F017CFA-5EAB-4285-8AED-77E14A717BCE’ while connection app ‘MyApp’ Error: Timed out waiting for device 7F017CFA-5EAB-4285-8AED-77E14A717BCE for client MyApp at file:///Applications/Flipper.app/Contents/Resources/app.asar/bundle.js:4209:5711

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:5
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

7reactions
nlindrooscommented, Feb 21, 2022

Fixed a similar issue by upgrading idb-companion from 1.0.14 -> 1.1.6.

This can be done by running

brew update && brew upgrade idb-companion

Found the underlying issue from the console in Flipper, (option + command + i to open console), where the command ~/Library/Python/3.8/bin/idb list-targets --json resulted in an error.

After upgrading idb-companion, the list-targets command succeeds.


@kbirgoren You should specify an exact version of Flipper in your Podfile, e.g. use_flipper!({ 'Flipper'=> '0.135.0' }) if you're using the most current recent version right now.
5reactions
gmontecommented, Feb 23, 2022

This works for me:

brew update && brew upgrade idb-companion

Fixed a similar issue by upgrading idb-companion from 1.0.14 -> 1.1.6.

This can be done by running

brew update && brew upgrade idb-companion

Found the underlying issue from the console in Flipper, (option + command + i to open console), where the command ~/Library/Python/3.8/bin/idb list-targets --json resulted in an error.

After upgrading idb-companion, the list-targets command succeeds.

@kbirgoren You should specify an exact version of Flipper in your Podfile, e.g. use_flipper!({ ‘Flipper’=> ‘0.135.0’ }) if you’re using the most current recent version right now.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting iOS Issues - Flipper
If during connecting iOS app to Flipper you see error message "Connection failed. Failed to find device <device_id> while trying to connect app"...
Read more >
Tweets with replies by Flipper (@flipper_fb) / Twitter
Failed to find device error on Flipper 0.133.1 · Issue #3432 · facebook/flipper. Bug Report As soon as I open the Flipper, I...
Read more >
Flipper Failing to Update - Flipper Zero Forum
Format the sd card on a pc, but uncheck “quick format” and then it should take up to an hour. When it is...
Read more >
Failed to find device error on Flipper 0.133.1 #3432 - bytemeta
This issue has been fixed in idb-companion 1.1.7. Make sure to uninstall the old version and install the new one since it supports...
Read more >
Desktop failed to provide certificates. Error from flipper desktop
At this point you won't have the same error message. (It will say that the certificate is ok.) However, if you encounter any...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found