Skip to content

[Bug] Wireless ADB Failed error message documentation is incomplete #263

Closed

Description

@djbclark

When a wireless ADB connection fails on macOS, 3 things are suggested: turning it on and then off again, etc.

What isn't suggested is what apparently actually needs to be done, at least in some cases: running "adb pair" from the command line.

If the user hasn't done this in a while, it's easy to forget that this can't be done within AirSync itself (from either side), so it can take some time to figure out that this is the way to fix things. I was looking all over the Airsync AIs on both sides for ADB pairing stuff and was flummoxed that I couldn't find it for a while, finally I did a search and found the right AirSync doc on the website.

Ideally, the app would handle this so the user never has to touch the command line, but just a doc update within the error message itself that pops up on the MacOS side when this is an issue would help a lot.

Note: This is likely also a bug in other desktop operating systems as well, but I use a Mac. It might also make sense to address it on Android, maybe some doc in the permissions screen, as a normal thing for a user to do is to look in the Android app for a re-authentication option.

Image

Activity

  1. sameerasw commented on Jul 18, 2026

    @sameerasw
    Owner

    Hi! In the upcoming version you will be easily able to pair the phone by scanning the ADB QR just like in Android Studio. That will eliminate the need of manually pairing with the CLI.

    Also I will try to improve the warning s and error messages with ADB but the issue is the adb errors themselves are never meaningful :(

  2. sameerasw commented on Sep 16, 2026

    @sameerasw
    Owner

    Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions