{ "id": "123212", "key": "TIMOB-16067", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "5", "description": "All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.", "name": "Cannot Reproduce" }, "resolutiondate": "2013-12-23T19:10:00.000+0000", "created": "2013-12-04T17:47:39.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "triage" ], "versions": [], "issuelinks": [ { "id": "33998", "type": { "id": "10002", "name": "Duplicate", "inward": "is duplicated by", "outward": "duplicates" }, "inwardIssue": { "id": "124181", "key": "TISTUD-5957", "fields": { "summary": "MAC Book Pro : No Android Devices Found ", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } } ], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2017-03-31T21:52:59.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10207", "name": "Tooling" } ], "description": "Using Titanium Studio, build: 3.2.0.201312031529 under windows 8.1, no Android Devices are found so an app cannot be compile or tested. Switching to Studio 3.1.2 using same SDK, devices are found. ", "attachment": [ { "id": "44781", "filename": "console.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2013-12-22T18:02:12.000+0000", "size": 3207, "mimeType": "text/plain" }, { "id": "44782", "filename": "mrahman_logs", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2013-12-22T18:02:12.000+0000", "size": 21928, "mimeType": "application/octet-stream" } ], "flagged": false, "summary": "Windows: No Android Devices Found", "creator": { "name": "andrew@gstreetmedia.com", "key": "andrew@gstreetmedia.com", "displayName": "Andrew Greenstreet", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "andrew@gstreetmedia.com", "key": "andrew@gstreetmedia.com", "displayName": "Andrew Greenstreet", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "Win 8.1 64 bit", "comment": { "comments": [ { "id": "284440", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "All, please try to reproduce the issue with the latest 3.2.0 SDK:\r\n\r\n* The original report indicates Studio 3.2.0.201312031529 (13 days old), but no indication of SDK version\r\n* [~mrahman] tried with SDK 3.1.3.GA, but no versions of 3.2.0\r\n\r\nPlease try with both the latest version of 3.2.0 SDK (and note the number). Also, try with the latest 3.1.3 SDK + 3.2.0 Studio (and note that specific version too)", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-12-16T15:11:22.000+0000", "updated": "2013-12-16T17:20:17.000+0000" }, { "id": "284511", "author": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Tested on the configurations below with the sample code given above, but could not reproduce. All the times the build was successful & the app launched successfully on the device.\r\n\r\nh6.CLI : 3.2.0-cr3 ----> Latest SDK: 3.2.0.v20131216064236 -----> Latest Appc Studio Appc : 3.2.0.201312151544 ----> Not Reproducible\r\n\r\nh6.CLI : 3.2.0-cr3 ----> SDK: 3.1.3.GA -----> Latest Appc Studio : 3.2.0.201312151544 ----> Not Reproducible\r\n\r\n\r\nh6.CLI : 3.2.0-cr3 ----> Latest SDK: 3.2.0.v20131216064236 -----> Latest Ti Studio : 3.2.0.201312142258 ----> Not Reproducible\r\n\r\nh6.CLI : 3.2.0-cr3 ----> SDK: 3.1.3.GA ----> Latest Ti Studio : 3.2.0.201312142258 ----> Not Reproducible\r\n\r\n\r\nh6.Tried from CLI 3.2.0-cr3 using SDK : 3.2.0.v20131216064236 ----> Not Reproducible\r\n\r\nh6.Tried from CLI 3.2.0-cr3 using SDK : 3.1.3.GA ----> Not Reproducible\r\n\r\nEnvironment:\r\nWindows : 8.1\r\nCLI : 3.2.0-cr3\r\nAppc Studio: 3.2.0.201312151544\r\nTi Studio : 3.2.0.201312142258\r\nTi SDK : 3.2.0.v20131216064236 , 3.1.3.GA\r\n", "updateAuthor": { "name": "lokeshchdhry", "key": "lokeshchdhry", "displayName": "Lokesh Choudhary", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2013-12-16T19:17:42.000+0000", "updated": "2013-12-16T19:56:43.000+0000" }, { "id": "285564", "author": { "name": "ngupta", "key": "ngupta", "displayName": "Neeraj Gupta", "active": true, "timeZone": "America/Los_Angeles" }, "body": "This issue needs further investigation. I noticed another issue on my machine today so it is a worthwhile for engineering to work directly with Mostafizur to diagnose this issue further. I will open another ticket for the issue I ran into.\r\n\r\n[~mrahman] Run the following command and attach the output here.\r\ntitanium info\r\n\r\nAttach build output log that shows the encryption error.", "updateAuthor": { "name": "ngupta", "key": "ngupta", "displayName": "Neeraj Gupta", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-12-22T08:49:24.000+0000", "updated": "2013-12-22T08:51:52.000+0000" }, { "id": "285570", "author": { "name": "michael", "key": "michael", "displayName": "Michael Gangolf", "active": true, "timeZone": "Europe/Berlin" }, "body": "\"adb devices -l\" lists my device but Ti 3.2 doesn't find it\r\n\r\nFedora Linux with 3.2 GA", "updateAuthor": { "name": "michael", "key": "michael", "displayName": "Michael Gangolf", "active": true, "timeZone": "Europe/Berlin" }, "created": "2013-12-22T14:16:56.000+0000", "updated": "2013-12-22T14:16:56.000+0000" }, { "id": "285574", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~michael] can you please post the results of running \"titanium info\" on the command line?", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-12-22T14:37:17.000+0000", "updated": "2013-12-22T14:37:17.000+0000" }, { "id": "285576", "author": { "name": "michael", "key": "michael", "displayName": "Michael Gangolf", "active": true, "timeZone": "Europe/Berlin" }, "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-12-22T15:12:36.000+0000", "updated": "2013-12-22T15:15:03.000+0000" }, { "id": "285577", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "thanks. Can you try running \"ti sdk select 3.2.0.GA\" and then re-running the \"ti info\" command?", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-12-22T15:17:45.000+0000", "updated": "2013-12-22T15:17:45.000+0000" }, { "id": "285581", "author": { "name": "michael", "key": "michael", "displayName": "Michael Gangolf", "active": true, "timeZone": "Europe/Berlin" }, "updateAuthor": { "name": "michael", "key": "michael", "displayName": "Michael Gangolf", "active": true, "timeZone": "Europe/Berlin" }, "created": "2013-12-22T16:05:46.000+0000", "updated": "2013-12-22T16:05:46.000+0000" }, { "id": "285588", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "To solve this, it should just be a matter of restarting ADB. That should fix [~michael]'s problem. Simply run:\n\n{code}\nadb kill-server\nadb start-server\n{code}\n\nIt is not uncommon that ADB gets in a weird state that is hard to detect.\n\nAccording to [~mrahman]'s log files, his problem has nothing to do with this issue. [~mrahman], please create a new ticket describing your problem with JavaScript encrypting include the log files with TRACE output. It's very important to have TRACE level output because it will show us additional debug information. You can enable trace logging by selecting \"Trace\" from Titanium Studio's console log level menu (generally in the lower right region). You can also set it at the command line by running \"ti config cli.logLevel trace\".", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2013-12-22T18:38:02.000+0000", "updated": "2013-12-22T18:38:02.000+0000" }, { "id": "285661", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "We're going to re-resolve this as \"Can't reproduce\" since the error here is specific to Windows. We feel the remaining issue is captured in TIMOB-16073 (for JavaScript encryption. We need a new issue for the error reported with Linux. One thought is that we explicitly test on Ubuntu, but not Fedora, and that might be the reason for the error. If you could please file a new ticket and mention it here, we'd be happy to investigate.", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-12-23T19:10:00.000+0000", "updated": "2013-12-23T19:10:00.000+0000" }, { "id": "288516", "author": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "updateAuthor": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-16T20:59:35.000+0000", "updated": "2014-01-16T20:59:35.000+0000" }, { "id": "288518", "author": { "name": "andrew@gstreetmedia.com", "key": "andrew@gstreetmedia.com", "displayName": "Andrew Greenstreet", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I found that you have to set your SDK using the CLI. If the CLI is stuck on an version of the SDK pre 3.2, then studio won't find the Devices.", "updateAuthor": { "name": "andrew@gstreetmedia.com", "key": "andrew@gstreetmedia.com", "displayName": "Andrew Greenstreet", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-16T21:04:06.000+0000", "updated": "2014-01-16T21:04:06.000+0000" }, { "id": "288540", "author": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Thank you, Andrew, for the suggestion.\r\nI now did a forced sdk install in the cli, so \"titanium sdk install 3.2.0.GA –force”, and I quitted Titanium and re-run it.\r\nNow the Run button is greyed out.\r\nUnder menu Run/Run Configurations I still get the message that no Android devices are connected.\r\nAlso now the \"ti info\" agian gives no answers anymore because of a permission problem (Error: EPERM, operation not permitted 'C:\\Program Files\\Windows NT\\Bureau-accessoires' which I also find very disturbing. ", "updateAuthor": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-16T23:10:36.000+0000", "updated": "2014-01-16T23:10:36.000+0000" }, { "id": "288551", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~erick] I think your error is related to TIMOB-16074.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2014-01-17T00:37:28.000+0000", "updated": "2014-01-17T00:37:28.000+0000" }, { "id": "288587", "author": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hi Chris, thank you for your reply.\r\nAfter pc restart, the \"ti info\" does again give normal information as listed above, so I cannot reproduce the EPERM error.\r\nNevertheless, I tried the solution that was suggested for the EPERM error (TIMOB-16074), but in my case there was no C:\\users\\..\\AppData\\Roaming\\Titanium\\mobilesdk\\lib, so I cannot remove the genymotion.js file.\r\nBut next time I get the EPERM error again, I will check carefully if I see a link to a file location like that.\r\n\r\nBut for now, I am still stuck.\r\nSo Ti info does give the information I listed above. And still no Android device is seen.\r\nAny idea how that problem could be solved?", "updateAuthor": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-17T06:49:12.000+0000", "updated": "2014-01-17T06:49:12.000+0000" }, { "id": "288635", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~erick] Can you see your device when you run {{adb devices}}? If yes, then run {{ti info -t android}} and you should see your device listed under Connected Android Devices. If you do not see your device under {{adb devices}}, then run {{adb kill-server}} and try again. If your device shows up in {{adb devices}} but not in {{ti info -t android}}, then ensure Titanium has the correct path to the Android SDK by running {{titanium setup android}} and try the steps above again.\n\nAlso, you have installed the Android USB driver, right? It's in {{C:\\path\\to\\android-sdk\\extras\\google\\usb_driver}}.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2014-01-17T18:13:06.000+0000", "updated": "2014-01-17T18:13:06.000+0000" }, { "id": "288837", "author": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Chris, I made a big step further thanks to your answer.\r\nIt must have had something to do with that usb driver indeed: the folder name you specified in extras did not exist. So I reinstalled android sdk with the extras for usb.\r\nNow at least Titanium does recognize my device. Thank you for that!\r\n\r\nI now get stuck in the next error, which may be related to the problem I had before. \r\nTitanium does see my device, I ask to Run on that device.\r\nIt says:\r\nBuilding for device.\r\n...\r\nForcing rebuild.\r\nThen it copies previous files to new locations that are apparently needed for the new Titanium version. So from Workspace\\projectname\\Resources to Workspace\\projectname\\build etc\r\nHaving done all of that, it says \"Encrypting Javascript files: C:\\...win32.exe ...\"\r\n32-bit titanium prep failed, trying using 64-bit\r\n\"Encrypting Javascript files: C:\\...win64.exe ...\"\r\n\r\nevents.js:72 throw er; // Unhadled 'error' event\r\n\r\nI saw other people having a similar error (http://developer.appcelerator.com/question/157016) \r\nIt was suggested to change environment variables. But which ones need to be updated? In http://docs.appcelerator.com/titanium/3.0/#!/guide/Software_Locations_and_Environment_Variables-section-29004844_SoftwareLocationsandEnvironmentVariables-WindowsSoftwareLocations the variables related to Titanium are all not available (N/A).\r\n\r\nSorry for all these questions...\r\n\r\n", "updateAuthor": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-20T16:48:05.000+0000", "updated": "2014-01-20T16:48:05.000+0000" }, { "id": "288860", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~erick] That's an easy fix. From the command line, run:\n\n{code}\ntitanium sdk install --force --default\n{code}", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2014-01-20T18:51:49.000+0000", "updated": "2014-01-20T18:51:49.000+0000" }, { "id": "289027", "author": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hi Chris,\r\nHm, no easy fix I am afraid.\r\nAs you said, I did \"titanium sdk install --force --default\".\r\nThe result was that after the install was ready, again it did not see my device anymore...\r\n\r\nI then saw that \"ti info\" also did not work anymore...\r\n\r\nSo I again deleted the genymotion file. That made \"ti info\" to work again.\r\nTitanium still did not see my device, but when I restarted the computer and rerun Titanium...\r\n...YES! \r\nIt runs!!\r\nTitanium does see my device, and I was able to install an app on it.\r\n\r\nGreat, thank you for all the help, Chris!!!", "updateAuthor": { "name": "erick", "key": "erick", "displayName": "Eric Kirchner", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-01-21T15:33:30.000+0000", "updated": "2014-01-21T15:33:30.000+0000" }, { "id": "416544", "author": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket with reference to the above comment that the issue is now fixed.", "updateAuthor": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2017-03-31T21:52:59.000+0000", "updated": "2017-03-31T21:52:59.000+0000" } ], "maxResults": 29, "total": 29, "startAt": 0 } } }