blog/developer-workflow-debug-and-junit/

[giscus[bot]]

blog/developer-workflow-debug-and-junit/

A walk-through of the new JDWP-based on-device debugging pipeline for ParparVM iOS apps and Android apps, with a step-by-step IntelliJ tutorial for each. Plus a short tutorial on the new standard JUnit 5 integration against the JavaSE simulator, with annotations for the visual configuration.

https://www.codenameone.com/blog/developer-workflow-debug-and-junit/

[DurankGts]

let me check if I understand well. this document told that it's possible to debug the CN1 App in a real device without need a mac? Explain me please.

On-device debugging that treats Java as Java
Codename One has always supported on-device debugging in the strict technical sense. You could attach Xcode to a .ipa, you could attach Android Studio to a running APK, you could read the native call stack, you could step through Objective-C or the C that ParparVM emits. What you could not do was set a breakpoint in MyForm.java, hit it on a real iPhone, and inspect a Java field on a Java object as a Java object. You also could not debug an iOS app without a Mac in the loop somewhere, because the only debugger that understood the binary was Xcode. The translation step between the Java you wrote and the C that ParparVM produces left no way back across the gap on the device.

PR #4999 (iOS) and PR #5012 (Android) close that gap. As of this week any JDWP-speaking debugger (IntelliJ IDEA, jdb, VS Code’s Java Debugger, Eclipse, NetBeans) can attach to a Codename One app and treat the running process as a JVM.

Supported targets:

iOS

the iOS Simulator (requires a Mac, because the iOS Simulator only runs on a Mac),
a real iPhone reached over Wi-Fi from the developer machine on the same network.
You do not need a local Mac to debug on a real iPhone. The Codename One build cloud runs the iOS build for you and produces a signed .ipa; install it on your iPhone the usual way (TestFlight, ad-hoc, or the standard Build Cloud install link), and the JDWP attach over Wi-Fi works from a Linux or Windows IDE just as well as from a Mac. The Mac is only required for the local Xcode build path and for running the iOS Simulator.

Android

the Android emulator,
a real Android phone over USB,
a real Android phone over wireless adb.
The Android attach uses standard adb, so you need the Android SDK platform tools installed on the developer machine. Those are available on macOS, Linux, and Windows, so any of the three is fine for Android debugging.

[DurankGts]

this just work using intell iDEA?

[DurankGts]

I set this

codename1.ios.onDeviceDebug=true
ios.onDeviceDebug.proxyHost=xxxxxx
ios.onDeviceDebug.proxyPort=55333
ios.onDeviceDebug.waitForAttach=true

but when I lanch my app in real device it's openg normally. I 'm using nb 30 jdk 17 in maven

[shai-almog]

You missed the arg prefix in all 4:

codename1.arg.ios.onDeviceDebug=true
codename1.arg.ios.onDeviceDebug.proxyHost=xxxxxx
codename1.arg.ios.onDeviceDebug.proxyPort=55333
codename1.arg.ios.onDeviceDebug.waitForAttach=true

It should work fine in all IDEs since the underlying mechanism is builtin to maven. To the IDE it just looks like it's connecting to a local debugging session.