Software Archive
Read-only legacy content
17061 Discussions

ERROR 20 - Debugging not pushing app to device

Carlos_C_4
Beginner
371 Views

I am running XDK 1816 on Win 8.1  with App Preview 2.2.4 and App Preveiw Crosswalk 0.27 on the device

I can see the device is connected in the debug window on the top left corner ...

I have App preview open on the device, and when trying to debug or  load the application on the device I get an error:

Error 20: Failed to Push files. Please Retry. File: unknown Cause: ERROR (1) from "core:private:http-request": Http request failed Error at new ComponentError (C:\Users\cc\AppData\Local\Intel\XDK\xdk\core-modules\public\component-error.js:17:1122) at Object.helpers_.makeError (C:\Users\cc\AppData\Local\Intel\XDK\xdk\core-modules\private\service\http-request.js:17:1933) at XMLHttpRequest.(C:\Users\cc\AppData\Local\Intel\XDK\xdk\core-modules\private\service\http-request-xhr.js:17:1903)

 

Any suggestion?

0 Kudos
7 Replies
Amrita_C_Intel
Employee
371 Views

Try starting App Preview on the device before you launch the app in the Debug tab. There were situations where slow devices (typical of the very inexpensive devices) need to have App Preview already up and running before you try to launch the app in the Debug tab.

Another thing is to insure that you have App Preview Crosswalk installed on your device, without it you cannot make the Debug tab work. Go to the "Apps" or "Applications" or "Apps Manager" section in the Settings area of your Android device and review the list of applications installed on your device. You should find both App Preview and App Preview Crosswalk (App Preview Crosswalk does not have a corresponding icon in the app start space on your Android device).

0 Kudos
PaulF_IntelCorp
Employee
371 Views

Sometimes duplicate copies of adb.exe on your machine can cause troubles. Using the Windows task manager you can kill any copy of adb.exe that is running, before you start the XDK, or simply update all the copies of adb.exe on your system so they are the same version (use adb --version to see what version each one is).

See this old forum thread for some help: https://forums.html5dev-software.intel.com/viewtopic.php?f=34&t=9430 and this doc page: https://software.intel.com/en-us/xdk/docs/configuring-your-windows-usb-android-debug-connection-for-the-intel-xdk

0 Kudos
Carlos_C_4
Beginner
371 Views

None of this is working... I am suspecting on the firewall / Intrusion Prevention System

Any workaround in this area?

 

0 Kudos
Tony_B_
Beginner
371 Views

I have similar problems getting the same error message and using win 7 and xdk 1816 and 1826. I would say my load fails about half the time, sometimes it works when I retry a second or third time and if that fails I shut down xdk and app preview on my Galaxy S4 then launch xdk again and it usually works.

 

0 Kudos
PaulF_IntelCorp
Employee
371 Views

There was also an issue where empty directories in your project directory or zero-length files would cause App Preview to hang up. I thought this was fixed, but double-check to see if that is part of the problem.

0 Kudos
puneet_d_
Beginner
371 Views

I resolved this issue by installing crosswalk runtime in device from playstore.

0 Kudos
Piter_O_
Beginner
371 Views

Just for the record, 

I was facing this issue too. I was able to debug one of the example apps, but with my I was getting this same error. 

As suggested on comment #2, I started the App Preview on the device before start the debug, and this solved the issue.

(I'm using Intel XDK3400.)

0 Kudos
Reply