Debugger Issues

[Bruce_D_1]

I'm having several issues with the XDK debugger. It's an either or - these issues don't occur at the same time, but one of them always occurs, rendering the debugger unusable:

1. Never finishes downloading the project to the device. I've left it running for up to an hour while doing other tasks. It never finishes.
2. Unable to download crosswalk to the device. Odd, cause it's already there.
3. Desktop error message flashes by too fast to read, and just displays 'You can now begin your remote debugger session'
4. It says it's running on my device, but there is just a black screen.
5. Error Failed to load resource: net::ERR_FILE_NOT_FOUND. It happens with different files each time.

As of yet, I have never had a successful debug session using XDK. As a baseline, I am able to debug the same app, as well as other apps, using NetBeans.

[Anusha_M_Intel1]

I am sorry to hear you are facing so many issues. We have a FAQ page on debug and  test questions here: https://software.intel.com/en-us/xdk/faqs/debug-test. You might be able to find some solutions. I see the crosswalk issue addressed. 

I am positive you have already looked through these documentation pages, but just in case:

https://software.intel.com/en-us/xdk/docs/using-the-debug-tab

https://software.intel.com/en-us/xdk/docs/intel-xdk-debug-and-test-overview

And I highly recommend you use our latest 1995 version if you aren't already. If you made an update from a previous version, you can try uninstalling and reinstalling it. 

[PaulF_IntelCorp]

What is the device you are using for debug? Some of the slower or low-memory devices are difficult to get a debug session started. Also, if your app is immediately doing lots of work, that can interfere with the debug initialization. If you change your app initialization so that it mostly just sets up the screen and then goes idle, waiting for user input, that can help. Or, for debug, modify your app so it does not try to immediately start downloading over the network or doing some other "work." Insert an "wait on event" before you do any of that to see if that allows the debug module to get started. The debugger is the standard Chrome DevTools that is being executed by the same interpreter that is executing your app, so too many cycles on the part of your app will interfere with that code getting started.