Debugging in XDK

[Adebayo_A_]

Good day everyone

I would like some help with the debug tab of the XDK

Whenever I build a custom debug module, my app works fine. But when I restart the XDK and connect my device, the XDK just show "Checking your debug module" and it gets stuck at that point.

I removed the debug module from my android phone and tried to use a generic debug module. After cancelling twice and explained in the documentation, it just show "Cancelling" and also gets stuck at that point.

Please any help will be deeply appreciated.

Thanks a lot.

[PaulF_IntelCorp]

It sounds like you are having a connection problem or, perhaps, your device is low on storage or RAM space.

Use the funny little paintbrush icon in the Debug tab toolbar (it's supposed to be a broom) to see if the XDK can see all of the debug modules installed on your device. If that works, it means you've got a good communication connection between your system and your device. If it lists a large number of debug modules, you might want to remove them from your device.

Also, see the list of trouble-shooting links near the end of this page > https://software.intel.com/en-us/xdk/docs/using-the-debug-tab

It could be that you did not check the "always allow" box on the "allow usb debugging" box (see about halfway down this page https://software.intel.com/en-us/xdk/docs/configuring-your-windows-usb-android-debug-connection-for-the-intel-xdk for an example image). If you fail to do that you will get a partial connection to the device. You have to remove the device from the USB, wait a bit and reconnect. Watch closely for this message and be sure to check the "Always allow" option so you don't have to do this every time you connect your device.

--- excerpt text below ----

Connect your Android device to your development system with a USB cable. When connecting your device to your development machine you may see an alert on the device requesting permission to allow USB debugging from this computer. Click Ok to grant the permissions required to debug your Android device with this computer.

If you see an alert on your Android device requesting permission to “Allow USB debugging,” click OK. On some slower Android devices there may be a delay of five or more seconds before you see an “Allow USB debugging?” alert.

Check the “Always allow from this computer” box to avoid having to watch for this alert the next time you attach your Android device for remote USB debugging.

[Adebayo_A_]

Thank you very much @Paul F.

I have a strong a connection with my cable and I have set the "Always Allow From This Computer". After sometimes, it finally shows the full Debug tab. But when I Click "Launch App on Device", It shows that it is transferring the files to my device and after sometimes, it writes "Error: Timed out after 5000ms". This happens with the profile tab too.

I used the brush tab to check installed debug modules and removed them. Does it means I have to build a debug module anytime I want to test my app on my device even if I have not made any changes to the app?

Also, I cannot install a generic debug module without an internet connection. Sometimes, I dont have an internet connection and I would like to be able to at least debug my apps even if with a generic debug module.

Thank you very much.

[PaulF_IntelCorp]

Hi Adebayo. Once you have installed a debug module, as long as you make no changes to the list of plugins that are part of your project or to the versions of those plugins, you shouldn't be asked to update it. Even if you do make such changes you can choose to keep using the already installed debug module (understanding that it might cause some code to break if, for example, your code now relies on a plugin that is not part of the debug module).

You need a network connection in order to build and download the debug module. You should not need one to install the generic debug module. Once either is installed, you should not need a network connection to work. But you may need the Internet connection to get a debug module installed.

I suggested removing all the debug modules in case you were running out of space. You don't need to do this every time you want to use the Debug tab, was only suggesting it as a way of debugging the issue.

Can you make a movie of what's happening and attach it here? I'm not sure I'm completely clear on the procedure you're using to make the generic module work. If I get time, I can try to make a movie to illustrate how to get to the generic module, but don't wait for that, I have very limited time...

[PaulF_IntelCorp]

BTW, did you try manually starting App Preview before you start debugging? On some devices you must do this by hand, if not, you can get the message you are seeing. This is one of the FAQ suggestions I sent you.

[Adebayo_A_]

@ Paul F. Thank you very much for the response.

I am sorry for the late response, my testing device got bricked and I had to find another one.

I will follow the steps you have mentioned and will get back to you.

I will make a movie about it and upload it.

Thank you very much.

[Adebayo_A_]

@Paul F.

I have fixed my device and I installed the latest XDK release with hot fix. I also installed the Early Access Version of the XDK.

The problems persisted in the normal XDK version, but it worked fine in the Early Access version.

I checked over and over again and then I noticed something.

In the normal XDK version, my device is recognized in the Debug and Profile tab, but when I go to Develop->Code, the device is not shown in the "Connected devices" section. I ran adb from command prompt and it shows my device is online.

In the Early Access version, the device shows in the Debug and Profile tab and also shows in in the "Connected Devices" section in Develop->Code.

I believe this is the cause of the problem. I have checked over and over again and its the same result.

I had to uninstall the normal XDK version and I am currently using the Early Access version for now.

I hope this gets resolved.

Thank you very much.

[PaulF_IntelCorp]

@Adebayo -- thank you for those observations. I'll get that info in front of the engineer responsible for that part of the XDK. I don't believe there was anything changed in the EA version that should have impacted that feature, so it might be difficult to pin down what is causing the problem. Regardless, I'll let engineering know.

[Ronaldo_M_]

I've never been able to use XDK Debug, it never worked for me. What I have done is to use Android Studio's logCat by filtering on error or info.