Android Question B4A 13 BETA - Waiting for the IDE Debugger to connect.

divinglog

Member
Licensed User
Longtime User
With the update to B4A 13 Beta, the overall APK size increazed and the first compile in debug mode slowed down. Because of that, the first debug run takes quite some time and when the app is finally installed on the device, the debugger does not connect anymore, resulting in this message which times out eventually:



The debug toolbar then looks like that (notice the stop button is not active anymore):



When I click the debug button again, everything is a bit faster and the debugger attaches correctly. But that means, I have to start the debug session two times. I'm not using the legacy debugger and I've increased the process timeout to 80 seconds, but I don't think this has an influence on the debugger attaching. The debug itself does not timeout, it's just the debugger that's not connecting.

I had the problem in the past as well, but not as often. Now with Beta 13 it is everytime on a fresh debug session.
 
Sort by date Sort by votes

divinglog

Member
Licensed User
Longtime User
I'm using B4A-Bridge, APK size is now 20.4 MB. Before 13 Beta and Target 34 the APK size was 6.9 MB.
 
Upvote 0

divinglog

Member
Licensed User
Longtime User
I've stopped the time and it takes about 2 minutes until the apk is installed and started at the very first debug run. The 2nd run takes 30 seconds until app start and the debugger connects without problems.

On the first run, the complile window also closes automatically at the end (not on the 2nd run)
 
Upvote 0

divinglog

Member
Licensed User
Longtime User
I've tested now USB debugging and the same happens on the first run. When I run debug mode again, I see this error in the log sidebar and the app starts:

B4X: 
java.lang.RuntimeException: java.io.EOFException
    at anywheresoftware.b4a.shell.Shell.virtualAssets(Shell.java:164)
    at anywheresoftware.b4a.shell.Shell.start(Shell.java:102)
    at anywheresoftware.b4a.ShellBA.raiseEvent2(ShellBA.java:105)
    at com.divinglog.divelog.main.afterFirstLayout(main.java:97)
    at com.divinglog.divelog.main.access$000(main.java:17)
    at com.divinglog.divelog.main$WaitForLayout.run(main.java:83)
    at android.os.Handler.handleCallback(Handler.java:958)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loopOnce(Looper.java:230)
    at android.os.Looper.loop(Looper.java:319)
    at android.app.ActivityThread.main(ActivityThread.java:8919)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:578)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)
Caused by: java.io.EOFException
    at java.io.DataInputStream.readFully(DataInputStream.java:205)
    at java.io.DataInputStream.readInt(DataInputStream.java:394)
    at anywheresoftware.b4a.shell.Shell.virtualAssets(Shell.java:136)
    ... 13 more
 
Upvote 0
You must log in or register to reply here.

Similar Threads

  • Question
Android Question Problems with USB-Debugger
Replies
3
Views
237
Cadenzo
  • Question
Beta B4A v12.5 BETA
Replies
8
Views
4K
netsistemas
  • Locked
  • Question
Android Question Something VERY wrong with debugger in V10
Replies
3
Views
1K
Erel
  • Locked
  • Question
Other B4A v5.80 BETA is released!
2
Replies
36
Views
20K
maurizio barbera
M
  • Article
Android Tutorial Rapid Debugger
2 3
Replies
47
Views
25K
klaus
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…