Android Question Rapid Debugger – just noticed

[canalrun]

Hello,
I downloaded and installed B4A version 3.0. I am working on an new app based on an older working app.

I installed the new app and tried to execute using the rapid debugger. After clicking open on the device, the main view of my app just flashed on the screen then the app exited and debugging stopped.

Using the legacy debugger I installed and executed. Execution halted in Activity_Create at the following line of code:

s = File.GetText(File.DirAssets, "aqhelp.html")

The problem is aqhelp.HTML does not exist for the new app. This line of code probably generated an exception. In the rapid debugger the response to this exception is the activity exited and the debugger closed – no break at the erroneous line of code.

In the legacy debugger execution breaks at this erroneous line of code.

By not breaking at the erroneous line I would say the rapid debugger did not handle this properly.

Barry.

 

[hypergreatthing]

Hello,
I downloaded and installed B4A version 3.0. I am working on an new app based on an older working app.

I installed the new app and tried to execute using the rapid debugger. After clicking open on the device, the main view of my app just flashed on the screen then the app exited and debugging stopped.

Using the legacy debugger I installed and executed. Execution halted in Activity_Create at the following line of code:

s = File.GetText(File.DirAssets, "aqhelp.html")

The problem is aqhelp.HTML does not exist for the new app. This line of code probably generated an exception. In the rapid debugger the response to this exception is the activity exited and the debugger closed – no break at the erroneous line of code.

In the legacy debugger execution breaks at this erroneous line of code.

By not breaking at the erroneous line I would say the rapid debugger did not handle this properly.

Barry.

I'm noticing the same thing. Rapid debugger just dies. I don't even see the crash in my log. I could sware that my device is disconnecting from abd as well since i have to disconnect and reconnect the device to install via compile.

 

[canalrun]

I want to add…

I am seeing this error in other situations also (although all my debugging is currently in Activity_Create). A subroutine was expecting a Typeface but I was giving it an Integer, the app and debugging session just closed with no info.

I also must add – Holy Cow the rapid debugger is nice.

Barry.

 

[JakeBullet70]

I noticed it does do this when the code is starting up. After that though it works as expected.

 

[PenguinHero]

For what its worth I've found a similar thing when using the rapid debugger. Some runtime errors cause the application on my tablet to just silently die.
If I look at the B4A environment I can see the Java exception in the log.

If I switch back to using the legacy debugger then I get the usual error info displayed on the the tablet.

 

[Erel]

The error should appear in the logs when you run it with the rapid debugger.

The error dialog doesn't appear in rapid debug mode. It doesn't appear due to the way exceptions are handled in the rapid debugger. However once you get used to checking the logs you will find it quickly.