[TIMOB-16168] Android: CLI does not detect Android device after upgrading to 3.2.0 release
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Needs more info |
|---|
| Resolution Date | 2014-08-26T20:44:47.000+0000 |
|---|
| Affected Version/s | Release 3.2.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | CLI |
|---|
| Labels | n/a |
|---|
| Reporter | jason hu |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2014-01-01T17:59:39.000+0000 |
|---|
| Updated | 2017-03-23T21:43:25.000+0000 |
|---|
Description
Steps to Reproduce
fresh installation of titanium 3.2, beta or even nightly,
plugin android phone, click refresh device list, go to run configuration, the device is not shown up, I can't develop android app with it at all.
however, it works fine with old titanium 2.0
Actual Result
android device not show up
Expected Result
android device shows up in the list
Attachments
I would appreciate if you can execute the following command and attach the output to this ticket and we would be happy to investigate it further. titanium info It is also possible that you may be missing the USB driver for this device. Please confirm that you have used the same device for development on this machine earlier.
As what I mentioned, it all worked fine before 3.2 update, so my device has no issues, besides, this is a Mac, no need for drivers. Please see attached txt
Can you please run the following command and see if it detects the device : adb devices
yes, it can always detect all my devices. I tried suggested dab kill-server/start-server as well
Please try running the following at the command line: {quote} adb kill-server adb devices ti info -t android {quote} If your device is listed in the "adb devices" output, then it's definitely connected. If it's connected, verify that the device is listed under the "Connected Android Devices" section of the "ti info" output. If it's not listed, then this can be caused by a number of things. Here's the most common that comes to mind: 1. Double check that the "state" of the connected device is "device". If it's not, then your device may be prompting you asking something like "allow usb debugging?" Make sure you say OK on the device. 2. If you have more than one Android SDK installed and you tell Titanium to use one, but you have the other Android SDK in your PATH. This will cause conflicts and mess things up.
thanks for the response. the command line can always detect my devices, my device was unlocked for debugging, since I have been using it for development for over 2 years; I only have android sdk installed; As I said, this all worked fine until I updated to 3.2 studio.
[~jason919] Hmm, ok. I wonder if this is a OS X Mavericks specific thing. I need more time to test. What device are you trying to use? Maybe we have the same device that I can use to try and reproduce the problem. In the meantime, is there another device you can test with?
I have tested galaxy s3, LG Optimus, Galaxy Note3, Nexus S, Atrix Moto, they all worked before 3.2, now they all can't be detected. BTW, I also tried to create a brand new user account and installed everything from scratch, and still didn't like it.
Moving this ticket to engineering for further diagnosis.
[~jason919] We believe this would be resolved by upgrading to the latest versions of all the tools. Can you please upgrade to Studio 3.2.3, CLI 3.2.3 and SDK 3.2.3 and see if that fixes the issue?
We're unable to proceed as we need more information. If you are able to provide us more guidance, we'd be happy to take a look.
It was resolved in 3.3 and 3.4. thanks for looking into it.
Closing ticket with reference to the above comment.