My WiFi seems to have issues this morning. When wifi drops out, my phone switches to 4G, but the connection with Kodular is lost. So I tried the USB connection. It reports a problem (actually a bug) when trying to connect with the companion on my phone. Eventually my App is shown, but pieces seem to be missing (my screen title is incomplete). This is what I get in the Starter:
Kodular Starter v2
OS: windows
ADB path: C:\Users<user>\AppData\Local\Temp\KodularStarter\adb.exe
Running a Vweb app on http://localhost:8004
Hit Ctrl+C to quit.
[INFO] Turn USB debugging on from the Developer Options on your phone
[INFO] Device found = 6ddd464
[INFO] Device found = 6ddd464
[INFO] Device found = 6ddd464
[INFO] Device found = 6ddd464
[INFO] Device found = 6ddd464
[INFO] Device found = 6ddd464
Failed first_line
Starting companion app on device [6ddd464] (Keep your phone connected via USB)8001
Starting: Intent { act=android.intent.action.VIEW cmp=io.makeroid.companion/.Screen1 (has extras) }
Warning: Activity not started, intent has been delivered to currently running top-most instance.
Failed first_line
[INFO] Resetting…
[INFO] Killed adb…
Failed first_line
[INFO] Resetting…
[INFO] Killed adb…
Failed first_line
Is this an issue with my ADB settings?