-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect on macOS: LIBUSB_ERROR_NOT_FOUND #121
Comments
I hit the same issue macOS 10.12.5
|
I think this is the message if OSX FUSE is not isntalled. Can you confirm that you have some FUSE FS mounted? |
Having similar symptoms here. Looks like the same output before/after installing OSX FUSE using osxfuse-3.6.3.dmg from their site, here's what I got after installing and rebooting:
|
Good news guys (seems to be outdated issue anyway), I had similar issue and found that calling
diff --git a/mtp/mtp.go b/mtp/mtp.go
index 3c90d5b..0524e22 100644
--- a/mtp/mtp.go
+++ b/mtp/mtp.go
@@ -146,6 +146,7 @@ func (d *Device) Open() error {
return err
}
+ d.claim()
if d.ifaceDescr.InterfaceStringIndex == 0 {
// Some of the win8phones have no interface field.
info := DeviceInfo{}
@@ -168,7 +169,6 @@ func (d *Device) Open() error {
}
}
- d.claim()
return nil
} I don't know if it's portable between serveral OSes but anyway it's working on my Mac. |
I was hacking my fork and it seems it works on Windows, macOS, and Linux. |
I have raised a PR with your patch. |
I built go-mtpfs from source but can't make it connect to my phone.
The debug output seems to show some MTP communication. The DeviceInfo retrieved doesn't seem obviously wrong. It's not clear why LIBUSB_ERROR_NOT_FOUND is printed first though.
Hardware
MacBook Pro (Retina, 15-inch, Mid 2015); MacBookPro11,5
HTC One X+
Versions
go-mtpfs: bc7c0f7
go-fuse: 6c2b7d8
usb: 69aee45
libusb: from Homebrew, described as: stable 1.0.20 (bottled), HEAD
FUSE for macOS: 3.5.4, installed without MacFUSE compatibility layer
macOS 10.12.2
Android 4.2.2
The text was updated successfully, but these errors were encountered: