Child pages
  • Debugging Mobile
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Servoy 7.3 uses the standard Chrome debug protocol to setup a debugger for a mobile application. For this to work the mobile client needs to be exported in debug mode, this must be done by using the mobile export (Export Soluton->Mobile Export) and then enable the "Export in debug mode" checkbox. If that mobile solution is then executed on a mobile or in the desktop browser, it will talk back to the developer. This talk back is enabled if you have/had a mobile solution enabled in the developer once. The developer will then startup a special service under: localhost:8889.

If the mobile solution is running, then you can open in the chrome browser that same url: localhost:8889. That will open directly a the mobile solution in the debugger, or will present you with 2 or more tabs if you have multiply tabs or instances of the mobile solution open. Then you need to select the right tab or close a few old tabs first.

In the debugger tab of chrome you have a few tabs where you can inspect stuff, like the Resources tab to see the loaded or stored resources, the console tab where you can see the console output the client generates or the scripting tab where you can start debugging your actual code that is running in the mobile client, the navigator to all the sources are in the navigator (the arrow button on the left). Under "(no domain)" section you will find the same scripts you also have in the developer. You can open them to set breakpoints, these will now be hit when you hit that code in the mobile client.

You can also push changes right to the running client by making changes directly in the chrome browser and save those changes. This will push the changes to the mobile client and that code will be executed in the next run. If you reload the client or start the phonegap application again then these changes will be lost. The changes you do here are reflected right away in the workspace of the developer.

 

  • No labels