Open mhaqqiw opened 3 years ago
Check if your adb path its correct and then
1-adb kill-server 2-adb start-server
that could help try.
note that Docker in MacOS and especially USB access inside containers are bit tricky and propose to forget trying ADB in container unless you really know what you are doing (deep understanding of virtual machines in MacOS).. If you run ADB directly in MacOS then it should work just fine but you have to configure docker-compose to get adb access from host side.
hi @jupe, did you have example accessing adb host through container? it will help me a lot. thanks before
Here is one forum which tries to get usb access working on MacOs: https://gist.github.com/stonehippo/e33750f185806924f1254349ea1a4e68 I have’t try it by myself and no idea does it work or not. When I faced this issue and get deeper I eventully giving up since it was not mandatory for me. ”workarounds” are using linux instead, or just run adb directly on MacOs host..
Anyway, I don’t think this issue is nothing to do with STF itself. Documentation could mention that usb access inside Container on MacOS is bit tricky and you are your own with it.. cc: @koral--
Host: MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports) OS: Big Sur (11.2.3)