topic Sometimes you need to start in Software Archive

Timed out in debug mode

Miguel_Ángel_M_ — Thu, 06 Oct 2016 09:51:00 GMT

Hi all,

When I try to debug my application in Intel XDK with a usb connect device (debug tab) an error is displayed ("Timed Out: 5000 ms"). The device is detected and I can access it via Windows Explorer. I test with the USB mode MTP and PTP and the error continue.

Next I copy a piece of log when you can see the error:

device:[2016-10-06T09:01:04.852Z]: (1475744464852): listPlugins failed:
Error: Timed out after 5000 ms
device:[2016-10-06T09:01:04.854Z]: (1475744464854): listSectionedDebugModulePlugins failed:
Error: Timed out after 5000 ms
client:remote-tab:[2016-10-06T09:01:04.854Z]: (1475744464854): needsDebugModuleCore failed:
{"code":"ETIMEDOUT"}
client:remote-tab:[2016-10-06T09:01:04.855Z]: (1475744464855): { [Error: Timed out after 5000 ms] code: 'ETIMEDOUT' }
client:remote-tab:[2016-10-06T09:01:04.856Z]: (1475744464857): undefined
client:remote-tab:[2016-10-06T09:01:04.858Z]: (1475744464858): [ 'console.trace (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/components/client/remote-tab/remote-tab.js:20:200)',
  'handleDebugModuleError (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/components/client/remote-tab/remote-tab.js:19:3463)',
  '_rejected (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/node_modules/q/q.js:844:24)',
  'Promise.when (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/node_modules/q/q.js:1122:31)',
  'Promise.promise.promiseDispatch (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/node_modules/q/q.js:788:41)',
  'runSingle (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/node_modules/q/q.js:137:13)',
  'flush (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/node_modules/q/q.js:125:13)' ]
client:remote-tab:[2016-10-06T09:01:04.862Z]: (1475744464862): timeout
client:adb:[2016-10-06T09:01:04.959Z]: (1475744464959): Rejected adb command with stderr Android Debug Bridge version 1.0.31

 -a                            - directs adb to listen on all interfaces for a connection


....................


 ANDROID_LOG_TAGS             - When used with the logcat option, only these debug tags are printed.
 "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver\adb.exe" reverse --remove-all
client:adb:[2016-10-06T09:01:04.959Z]: (1475744464959): {"killed":false,"code":1,"signal":null,"cmd":"C:\\Windows\\system32\\cmd.exe /s /c \"\"C:\\Program Files (x86)\\ClockworkMod\\Universal Adb Driver\\adb.exe\" reverse --remove-all\""}
client:remote-tab:[2016-10-06T09:01:04.971Z]: (1475744464971): [ 'console.trace (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/components/client/remote-tab/remote-tab.js:20:200)',
  'toast (file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/components/client/remote-tab/remote-tab.js:18:4850)',
  'file:///C:/Users/david/AppData/Local/Intel/XDK/xdk/components/client/remote-tab/remote-tab.js:19:3323' ]
device:[2016-10-06T09:01:05.125Z]: (1475744465125): ws onerror: Error: connect ECONNREFUSED

---------------------

Thank you in advance,

Miguel Ángel

Sometimes you need to start

PaulF_IntelCorp — Thu, 06 Oct 2016 17:25:43 GMT

Sometimes you need to start App Preview on the device before you attempt to start the debug session on the Debug tab. If that doesn't work, you may have insufficient space on your device or it may be a very slow device. In that case, try another device or try using this technique > https://software.intel.com/en-us/xdk/docs/intel-xdk-debug-and-test-overview#RemoteChromeDevTools <

Thanks Paul:

Miguel_Ángel_M_ — Fri, 07 Oct 2016 06:08:51 GMT

Thanks Paul:

I think is not a device problem because I can debug it in another PC and at same PC I can't debug with other devices. For that reason I think is a PC configuration problem. Is there any way to change the debug timeout in Intel XDK?

On the other hang, the technique you propose requires build app and install it in the device every time you make a change in your code, isn't it? And it is very slow procedure.

Miguel -- there is no way to

PaulF_IntelCorp — Fri, 07 Oct 2016 15:33:34 GMT

Miguel -- there is no way to change the timeout.

Regarding the alternate build option, you don't need to rebuild your app for all debugging. It's possible to redefine many functions in your app "on the fly" via the remote JavaScript console. What you can redefine depends on how you have written your app and defined your functions. See this video > https://software.intel.com/en-us/videos/using-the-test-tab < at about position 19:30, which illustrates what I mean (the video, at that point, is using weinre to debug a built app, but the same "redefine" technique applies to debugging a built app with remote CDT).