Testing and debugging an application on an Android device

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

This content has been translated automatically. Click here to view the French version.

Help / Developing for Android

Overview
How to?
Launching a test/debugging project in Android
Associating a new wireless device
Remarks
InTestMode function
Add the debug application generated to your Firebase console
Unavailable features

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

Testing and debugging an application on an Android device

Overview

Application testing and debugging directly on the hardware is appreciated by all developers.

WINDEV Mobile enables you to test and debug functions directly on the phone that cannot be emulated efficiently on the PC: GPS position, on-board printer, scanner, access to contacts and the phone's calendar, photo and video capture, gestures (line deletion by swiping, etc.), etc.

The principle is simple: When the project is run in "Debug on mobile device" mode:

the Android application is generated under a specific name (GO <Nom du projet>)
the application runs on the Android device connected to the development workstation (via USB or Wi-Fi).
New in SaaS
Attention Wi-Fi debugging is only available with WINDEV Suite SaaS 2025 Update 2.
For more details, see Using new features exclusive to WINDEV Suite SaaS 2025.

You can add breakpoints in the WLanguage code. As soon as a breakpoint is encountered, the debugger will automatically be launched on the development computer.

How to?

Launching a test/debugging project in Android

To debug a project in Android:

Test the project via the quick access buttons:
If the application has never been generated, a warning message proposes to launch the Android application generation wizard.
Note: the generation wizard can also be run if major changes have been made to the application (addition of a Map control, etc.).
The application is generated.

Several cases may occur:

If an Android device is physically connected to the development station (via USB), the application launches automatically on this device. The code editor is displayed in debugger mode on the development computer.
In other cases, the list of available devices is displayed:

Use this list to select the desired device.
To appear in this list, the device must:
- be connected to the device and allow USB debugging.
- New in SaaS
  or be linked via wifi.
Simply select the desired device to launch the application in test mode.

New in SaaS

Associating a new wireless device

In the list of available devices, you can add a new wireless device ("Connect a wireless device" button).

Activate the developer mode on your device as well as the "Wireless debugging" mode. For more details, see Preparing the Android phone for testing.
In the device selection window, click on "Connect a wireless device".
In the window that appears, enter the information from your device:
Enter the validation code on your device.

Note: This feature is only available from WINDEV Suite SaaS 2025 - Update 2.

For more details, see Using new features exclusive to WINDEV Suite SaaS 2025.

Remarks

Stopping the debugging on the development computer does not close the application on the Android device.
When testing via USB, it is possible to disconnect the device from the PC and continue using the application. However, if the application is closed, the test can be run only if the device is reconnected to the PC.
The debugger is not available on an emulator.
The Android Control Center allows you to see the traces and debug information of the application being tested.

InTestMode function

InTestMode returns True in the following cases:

If the project is tested on the device from WINDEV Mobile.
If the <Project name>.go application is launched on the Android device.

Add the debug application generated to your Firebase console

The new debug application package generated by WINDEV Mobile has the same name as the original application package with the ".go" extension. For example, if the name of your application package is "com.wmsport.android", the name of the debug application package will be "com.wmsport.android.go".

If you use Google services that require enabling Firebase in your application (such as push notifications):

Also add the debug application to the Firebase console (for more details, see Android configuration for push notifications (Firebase)).
Download the new google-services.json file including both applications, in order to provide it instead of the previous one.

Unavailable features

Some features of the debugger are not available in this version:

F8 to change processes or events.
Set next statement.
Particular breakpoint modes (ignore intermediate breakpoints, ignore timers, etc.).
Automatic evaluations (current line of code identifiers, return values, local and global variables, members of the current class (this), HFSQL (Out, Error, etc.), WLanguage (Error, etc.)).
HFSQL information (data files, queries, etc.).
System information (critical sections, semaphores, etc.).
Save the results of a query.
Fix and continue.
Audit, profiler, memory.
Display values of non-simple variables (structures, xml, json, arrays, etc.)
Stop declarations of simple types for which no value is assigned.
Example:
n is an int // The debugger cannot stop at this line
n is an integer = 3 // The debugger can stop at this line.

New in version 2025
New features are available in this version:

Breakpoints in internal procedures.
Breakpoint in procedures with automations.
Traces, errors and exceptions can be viewed directly in the debugger's dedicated pane.
Better display of advanced types in the debugger.
Run to cursor functionality.