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.

Android app running on Android Q emulator doesn't show up in Flipper

See original GitHub issue

Android app running on Android Q emulator doesn’t show up in Flipper. I have this errors in Console:

Failed to create adb client using shell adb command. Trying with adbkit.
Error: Command failed: /opt/android_sdk/platform-tools/adb start-server
/bin/sh: /opt/android_sdk/platform-tools/adb: No such file or directory

Error: Command failed: /opt/android_sdk/tools/emulator -list-avds
/bin/sh: /opt/android_sdk/tools/emulator: No such file or directory

"FailError: Failure: 'cannot bind listener: Operation not permitted'
    at file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:59600:31
    at tryCatcher (file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:58596:27)
    at Promise._settlePromiseFromHandler (file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:56591:37)
    at Promise._settlePromiseAt (file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:56674:22)
    at Async._drainQueue (file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:53969:16)
    at Async._drainQueues (file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:53974:16)
    at MutationObserver.Async.drainQueues (file:///Applications/Flipper.app/Contents/Resources/app/bundle.js:53841:18)
    at process._tickCallback (internal/process/next_tick.js:68:7)"

Flipper 0.21.0

Issue Analytics

State:
Created 4 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

3reactions

jknoxvillecommented, Jun 10, 2019

I think this is probably due to Flipper not currently having a good way to deal with custom android sdk installation locations. It looks for an ANDROID_HOME env variable, and falls back to /opt/android_sdk/.

However, env variables set in .bashrc files and similar aren’t loaded for GUI applications, unless you launch them from the terminal.

One way to workaround this would be to either move your android_sdk to /opt/ (though expect to have to update android studio and any other tools that know where it currently is), or symlink it (ln -s /path/to/your/sdk /opt/android_sdk)

0reactions

passycommented, Sep 25, 2019

I’m cleaning up some old issues and this one hasn’t seen updates in a long time. Please let me know if this is still a problem and we can reopen it. Thanks!