Im try to testing debug on something, but as i can’t create any other project except my android project, i try to debug on connected android device but this is not showed on the lids of devices? Is ok or the android must appear there and in this release is already possible to debug on devices?
Best regards.
This should work. Does the device show when you run “adb devices” from the command line?
-bash: adb: command not found
Sounds like i have a big problem with adb. Strange because i have android studio installed.
BTW, im uisng a real android device and it works debugging with android studio. Any idea what to check?
Even wird
I find dab path, is the same where fire points but…
That is the output:
MacBook-Pro-de-German:~ germanpablogentile$ /Applications/Android\ Studio.app/sdk/platform-tools/adb devices
List of devices attached
While the device is connected and i can’t run debug on this device from android studio. I will lost my hair…
Weird. this is the list we go by. if it doesn’t show there, then we and the Android SDK aren’t seeing your device. Is Android Studio running on your Mac, as well? or do you by chance run that in a VM and have your android device connected thru to that?
Sorry, i explain it bad.
Android Studio: running on my Mac, yes i CAN run and debug on the Android Tablet.
Fire: same Mac, same android tablet, CAN´T run with debug on the Android Tablet.
k.i don’t know what magic Android Studio does. “adb” is what we use. if adb doesn’t see the device, something is wrong that is outside of my control.
Ok. i will investigate this and tell you, I guest will not be the unique with this problem.
Ok, that start to be even more strange:
MacBook-Pro-de-German:~ germanpablogentile$ /Applications/Android\ Studio.app/sdk/platform-tools/adb devices -l
List of devices attached
20080411413fc082 device usb:1D113000
But in Fire still see:
Any idea?
marc,
This work with crossbow? Theres any special sequence to follow?
i remove android studio and start installing all by hand and still is not detect on fire.
no, this is all handled internally in Fire — it runs adb devices. It does so every ~30s, so if the device does show up in abd for you, it should also show in Fire within 30s, and/or after a restart. DO you see any messages in Console.app that would indicate Fire could not run adb?
I see this:
30/05/14 15:09:06,464 com.apple.mtmd[70]: Failed to get the path for fd 5 (Invalid argument)
30/05/14 15:09:17,816 Fire[3829]: FillTypes2: or FillMembers3:: Exception: Null Reference Exception
Is the only error message
my adb is under platforms_tools btw…
/Users/germanpablogentile/Code/Others/android-sdk-macosx/platform-tools
and the SDK path on fire is
/Users/germanpablogentile/Code/Others/android-sdk-macosx
MacBook-Pro-de-German:platform-tools germanpablogentile$ ./adb devices
List of devices attached
20080411413fc082 device
Ok, i’ll get you a new build over the weekend, with extra logging for the adb code.
I wil waiting this, thanks!
New build going up for you.you should see something like:
2014-06-02 11:06:35.490 Fire[52392:5c07] running /Users/mh/Downloads/adt-bundle-mac-x86_64-20131030/sdk/platform-tools/adb devices -l
2014-06-02 11:06:35.501 Fire[52392:5c07] adb: List of devices attached
2014-06-02 11:06:35.501 Fire[52392:5c07] adb: 015d14fec123fa18 unauthorized usb:20313000
2014-06-02 11:06:35.510 Fire[52392:5c07] device: 015d14fec123fa18 unauthorized usb:20313000 (unauthorized)
2014-06-02 11:06:35.510 Fire[52392:5c07] adb:
This is the output here
02/06/14 11:03:50,356 Fire[76712]: running /Users/germanpablogentile/Code/Others/android-sdk-macosx/platform-tools/adb devices -l
02/06/14 11:03:50,371 Fire[76712]: adb: List of devices attached
02/06/14 11:03:50,372 Fire[76712]: adb: 20080411413fc082 device usb:1D114000
02/06/14 11:03:50,372 Fire[76712]: device: 20080411413fc082 device usb:1D114000
02/06/14 11:03:50,372 Fire[76712]: adb:
02/06/14 11:03:50,403 Fire[76712]: Exception running adb. Giving up. Null Reference Exception
curious. will need to add more logging tomorrow.
if you need teamviewer access just let me know (we have only version 8 licensed)
maybe, thanx. for now, i think logs will be enough.
Sorry for the delay; it’s been a busy week. I’ve uploaded a new build to dropbox for you, Fire-Debug-Android-v2.zip. This fixes one potential NRE, and also emits way more logging that should help narrow it down if that fix didn’t do the trick.