I used to have this error when B4A was installed in my old Laptop. After I change the IDE to a new Intel NUC, 64GB Ram, never saw this problem until yesterday.
No new software was installed in the NUC, no new apps were installed or uninstalled from the device. I try to deploy in two different devices, with the same error. Changing to Legacy Debug will do the work, but it is a pain to work with the debugger in legacy mode. Also, it works in Release, so I assume that has something to do with the debugger.
The code also was not changed at any point from when it started to crash. Up to now the following things have been done:
Disable A/V
Disable WIN Firewall
Disconnect network (unplug cable)
Restart device(s)
Restart computer
Restart ADB Server
Kill ADB Process (Task Manager)
I am sure there must be some kind of file lock somewhere, but I cannot find a way to know which one crashes the debugger. It is really annoying to get this error and at this point having no clue where to look at. I have seen many threads through this forum, but none of the points to the real problem. Up to know I don´t know where else to scratch to find a definite solution to this problem. Has some found really where this is pointing? A new project would compile with no problem. But as I said, no code was changed, not a single warning in the logs to watch out.
No new software was installed in the NUC, no new apps were installed or uninstalled from the device. I try to deploy in two different devices, with the same error. Changing to Legacy Debug will do the work, but it is a pain to work with the debugger in legacy mode. Also, it works in Release, so I assume that has something to do with the debugger.
The code also was not changed at any point from when it started to crash. Up to now the following things have been done:
Disable A/V
Disable WIN Firewall
Disconnect network (unplug cable)
Restart device(s)
Restart computer
Restart ADB Server
Kill ADB Process (Task Manager)
I am sure there must be some kind of file lock somewhere, but I cannot find a way to know which one crashes the debugger. It is really annoying to get this error and at this point having no clue where to look at. I have seen many threads through this forum, but none of the points to the real problem. Up to know I don´t know where else to scratch to find a definite solution to this problem. Has some found really where this is pointing? A new project would compile with no problem. But as I said, no code was changed, not a single warning in the logs to watch out.
B4X:
Logger connected to: AGT4C19322013008
--------- beginning of crash
--------- beginning of system
--------- beginning of main
java.lang.RuntimeException: Unable to create service cl.abreme.android.starter: java.lang.RuntimeException: java.io.EOFException
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4535)
at android.app.ActivityThread.access$2600(ActivityThread.java:296)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2243)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:213)
at android.app.ActivityThread.main(ActivityThread.java:8178)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1101)
Caused by: 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:92)
at cl.abreme.android.starter.onCreate(starter.java:34)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4521)
... 8 more
Caused by: java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:200)
at java.io.DataInputStream.readInt(DataInputStream.java:389)
at anywheresoftware.b4a.shell.Shell.virtualAssets(Shell.java:136)
... 12 more
