Android Tutorial Rapid Debugger

Jack Cole

Well-Known Member
Licensed User
Longtime User
What is the expected behavior of the rapid debugger when a programming error is encountered when running an app (such as a null pointer exception)? It has always just crashed out of the app and exited rather than pausing as the legacy debugger does. It does not take me to the line number where the error is. I have tried this in multiple apps and on multiple machines with the same results.
 

kiki78

Active Member
Licensed User
Longtime User
I can't use Rapid Debugger with B4A 4.30

Legacy Debug and Release works fine, but when I try Rapid Debug, I receive message box with :

An error occurred.
Rapid Debugger failed to connect to device. Please try to run again.

Compilation and installation is ok, but this message appear just after.

I try with USB and B4A-Bridge and the result is the same.

I try to downgrade to 4.00 and Rapid work fine, then reinstall 4.30 and Rapid don't work.

Any idea ?

Regards
 

Dave O

Well-Known Member
Licensed User
Longtime User
If I'm running the rapid debugger and I make a change in the Designer (and save the change), it doesn't seem to take effect until I quit and restart the debugging session.

Is there a way to make UI changes in the Designer while the RD is running?
 
Cookies are required to use this site. You must accept them to continue using the site. Learn more…