Trouble connecting to ADB server on OS X about madb HOT 9 CLOSED

Hi @PhilippCh ,

Thanks for the detailed bug report!

I looked into this, and you are correct, a normal TCP endpoint is used by adb on all systems.

I was misled by the one exception - Debian (and hence also Ubuntu) has manually patched adb to listen on local sockets and Ubuntu was the Unix system on which we tested.

So the correct behavior would be to use TCP sockets on all operating systems, except for Debian Linux and derivatives.

I'll fix it for OS X, and keep this issue open to track a solution for Linux.

from madb.

For OS X, should be fixed by v2.0.247 of our NuGet package. Let me know if this helps.

from madb.

Unfortunately, this does not solve the problem. PlatformID on many OS X devices is still returned as PlatformID.Unix.

Here's a fixed version of Environment.OSVersion.Platform that checks whether certain Mac-specific directories exist on the machine. I would create a pull request, but I'm not sure whether you'd want to include this "hack" in the official version.

public static PlatformID GetCurrentPlatform() {
            var platformId = Environment.OSVersion.Platform;

            if (platformId == PlatformID.Unix) {

                // Well, there are chances MacOSX is reported as Unix instead of MacOSX.
                // Instead of platform check, we'll do a feature checks (Mac specific root folders)
                if (Directory.Exists("/Applications")
                    & Directory.Exists("/System")
                    & Directory.Exists("/Users")
                    & Directory.Exists("/Volumes")) {

                    platformId = PlatformID.MacOSX;
                }
            }

            return platformId;
        }

(Credit goes to http://stackoverflow.com/questions/10138040/how-to-detect-properly-windows-linux-mac-operating-systems)

from madb.

Thanks, I guess the best way would be to just make sure ADB is always listening on a TCP port and not on a Unix socket.

I'll look into this & get back to you.

from madb.

@PhilippCh, sorry for that!

Can you give v2.0.257 a try? In that version, we always assume the connection will be an IP connection (that's the default for adb); if anyone wants to use madb on a Debian/Ubuntu server they can manually specify a UnixSocket and we'll connect to that socket instead.

Long story short, should work out of the box now unless you're on Debian/Ubuntu and using their patched version of adb.

from madb.

Seems to be working fine now, thanks a lot! 👍

With the new build I'm receiving this error (http://stackoverflow.com/questions/31992705/vs2015-project-no-longer-runs-in-debug-mode) for SharpAdbClient.dll though. Any way around that?

from madb.

@PhilippCh , I'm guessing you're seeing this error because we include the debug symbols for SharpAdbClient in the NuGet package.

Just to test this theory, could you try to delete the SharpAdbClient.pdb file in packages\SharpAdbClient.2.0.254\lib\net45 and your project's output folder, and let me know whether you still get this error message?

Thanks!

from madb.

Unfortunately, this didn't fix the issue. I do have the SharpAdbClient.Extensions project in my solution (if that makes a difference), though like in the StackOverflow I linked, all configurations are set to Debug/x86.

from madb.

This issue is quite old. The original problem - macOS compatibility - has been fixed and I've never been able to reproduce the other behavior.

Feel free to open a new issue if you're still having a problem with this using the latest version of SharpAdbClient, though.

from madb.