[AC-5586] Studio Android losing device connection
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Resolved |
| Resolution | Needs more info |
| Resolution Date | 2018-03-18T21:44:32.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Studio |
| Labels | n/a |
| Reporter | Raymond Verbruggen |
| Assignee | Shak Hossain |
| Created | 2018-02-09T08:36:32.000+0000 |
| Updated | 2018-05-08T20:21:58.000+0000 |
Description
Studio 5.0.0.201712081732
Ti SDK 6.3.0
HTC one M8
Android 6.0
Testcase: create whatever project and run it on a connected Android Smartphone.
In about 50% of the cases it cannot install and run the app on the device:
[ERROR] : Unable to find device "SH44NWM12184"
[ERROR] Application Installer abnormal process termination. Process exit value was 1
[ERROR] Application Installer abnormal process termination. Process exit value was 1
Next I need to run again and sometimes it installs properly, and sometimes I need to unplug the device, and run again before it installs and runs.
All this time the device is connected with a (new) cable and not moving (taped it to my desktop).
Are there more people having the same issue?
Additional info: Sometimes I cannot run at all. But the cable connection is still present; I check that with "Android File Transfer". Using this program I can browse the file system without any problem. Only when I give a "appc appcd stop" command I can run again.
Hello, Is this only for your HTC one M8 device? Can you try on any other device and see if the problem occurs there or this just for HTC one M8. Let us know. Thanks.
Hello [~ray@raymondverbruggen.nl], Can you please get back to us about the above query?
Hello! Sorry I was away for the weekend and all day in my car driving. Yes I tested with HTC one M3, Samsung S7, Samsung S3, Nexus
Hello, Are you trying with the same cable for the different device? This looks like the cable issue as you mentioned this occurs randomly. I would suggest you try with the device dedicated cable and see if the issue occurs? There is no clear log on this issue. make sure your device "stay awake" in developer mode is selected. Thanks.
Yep "stay awake" is on. The cable is the same, it is a brand new one (of course I tested that first), and fixed by tape on my desktop so no loose contact. It is definately not a cable issue. In between while Studio says it has lost connection, I can still read from it with Android File Transfer. Also when I give the command "appc appcd stop" it can run again so the cable physical connection is still there.
Hello, Can you try with the latest SDK 7.0.2.GA? you are using an old SDK. Let us know. Thanks.
yes i will next friday, I am abroad :) I come back to you on friday
Sorry I cannot test that. In tiapp.xml I updated the SDK from 6.3.0 to 7.0.2 but that gives the following error. [ERROR] : Found incompatible Titanium Modules: [ERROR] : id: com.logicallabs.bluetoothle version: 1.2.9 platform: android min sdk: 6.1.0.GA [ERROR] : id: com.logicallabs.bluetoothle version: 1.2.8 platform: android min sdk: 3.1.0.GA [ERROR] : id: com.logicallabs.bluetoothle version: 1.2.10 platform: android min sdk: 6.1.0.GA [ERROR] : id: com.mirasense.scanditsdk version: 5.3.3 platform: android min sdk: 6.0.0.GA [ERROR] : id: com.mirasense.scanditsdk version: 5.3.1 platform: android min sdk: 6.0.0.GA [ERROR] : id: com.mirasense.scanditsdk version: 5.0.1 platform: android min sdk: 6.0.0.GA [ERROR] : id: com.mirasense.scanditsdk version: 4.15.0 platform: android min sdk: 2.1.0.GA [ERROR] : id: com.mirasense.scanditsdk version: 1.1.2 platform: android min sdk: 2.1.0.GA [ERROR] : id: com.logicallabs.bluetooth version: 1.1.0 platform: android min sdk: 6.1.0.GA [ERROR] : id: com.logicallabs.bluetooth version: 1.0.4 platform: android min sdk: 3.0.2.GA [ERROR] : id: com.logicallabs.bluetooth version: 1.0.3 platform: android min sdk: 3.0.2.GA [ERROR] : id: com.logicallabs.bluetooth version: 1.0.2 platform: android min sdk: 3.0.2.GA [ERROR] Application Installer abnormal process termination. Process exit value was 1 Hans Knochel already told me that modules have to be updated, but cannot find anything about that in the SDK7 release notes. These are modules from others, it is my experience during the last years that there are only a few will update, but most of them simply do not. So we will be stuck to 6.3.0. So this means that older SDK's will still have to be supported. Such breaking changes are very easily thought of by Axway...
Hello, These modules are third-party modules, For an update you need to contact those module developers for an update. Now, why don't you try on a new app (hello world), with the latest SDK. And see if the connection issue happening in there or not. Thanks.
[~ray@raymondverbruggen.nl],I just wanted to follow up with you about this issue.Did you manage to follow the instructions provided earlier ? Please let us know if you need more help with this issue.
Not yet, first I need to catch up the time I lost because of other issues. But this is definitely on my list. Good day and best regards, Raymond
Hello [~ray@raymondverbruggen.nl], Can you please follow up here. What's the update of your issue?
Hello and good morning! Still waiting for a solution. Some apps use third party modules which will not be updated for SDK 7. Some use appcelerator modules like Ti.UDP which is not updated for SDK 7. You cannot expect existing apps which require small updates to be updated to SDK 7. There is no one which is willing to pay for that. They will remain using the SDK which they were published with, so a fix for this problem is really needed! The development cycle is large because the message about losing connection is at the end of the compiler phase. And it is not disconnected as I already described... So please provide a decent solution or give the possibility back for debugging "the old way" which worked superb! Best regards, and have a great day! Raymond
Hello, Looked through the log again, and maybe have some more info: First it says it is building for SH44NWM12184, and at the end it fails on the same device. So the device is found.... Search for SH44NWM12184 in the text below, maybe it helps. Appcelerator Command-Line Interface, version 7.0.3 Copyright (c) 2014-2018, Appcelerator, Inc. All Rights Reserved. 2018-05-08T20:05:36.749Z | TRACE | set environment to {"registry":"https://registry.platform.axway.com","baseurl":"https://platform.axway.com"} 2018-05-08T20:05:36.751Z | TRACE | checking credentials for existing session 2018-05-08T20:05:36.923Z | TRACE | Attempting to load session info from config file 2018-05-08T20:05:36.931Z | TRACE | check if session is invalidated 2018-05-08T20:05:37.807Z | TRACE | refresh session expiry to: 1526414737695 2018-05-08T20:05:37.808Z | TRACE | session expiry 1526414737695 false 2018-05-08T20:05:37.809Z | TRACE | Arrow Cloud config file: /Users/raymond/.acs 2018-05-08T20:05:37.810Z | TRACE | found Arrow Cloud login { mid: '2d67571461c369d8ca16826cc35e164e5d7fc77a', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', username: 'ray@raymondverbruggen.nl', cookie: [ 'connect.sid=s%3ARSrGyxGo7b8qozNP8AVVCrlD1mDFh0xr.vI%2Bi1AaVHKn14yt3CAOFm%2By%2B2aiW%2FjcmxLvW9lJBOMI; Path=/; Expires=Wed, 16 May 2018 04:59:06 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise.appcelerator.com 2018-05-08T20:05:37.810Z | TRACE | Arrow Cloud cookie expiry [ 1526446746000 ] 2018-05-08T20:05:37.811Z | TRACE | session already loaded in opts.session 2018-05-08T20:05:37.812Z | TRACE | getCredentials() session: { "ipaddress": "192.168.1.14", "username": "ray@raymondverbruggen.nl", "password": "