Android Question B4A 9.30 mode debug problem


Active Member
Licensed User

Hello I have the following problem: When I run my code integrated with Firebase, the debug mode closes when it finishes downloading the installation, I use Bridge B4A, besides it delays in an excessive way the execution of the code, it is not a very big code. If I run the same code with an Android 24 emulator, debug mode works, but I can not use it with Firebase since it does not work with this feature. I have to try several times to be able to execute it in debug mode, and I can not move too far. Is there any possible solution? My laptop has an Intel icore5 7th gen regards


Licensed User
I have to try several times to be able to execute it in debug mode
Does that mean: after trying several times, your program eventually (sometimes?) executes in debug mode?

Sometimes in the heat of programming battle, the obvious can be forgotten, or shortcuts taken, so (at the risk of appearing to teach you to suck eggs)...

I haven't used Firebase, but when I experience problems of a similar vein, then:

First thing I would try is restart every device that is part of the debug chain (computer, router, Android device) ie turn them *all* *off* and then turn them on again. Presumably you've already tried this.

Second thing I would try is to remove the likely culprit. Can you do that with Firebase? You might need to create a dummy object with methods and properties so that the rest of your program at least compiles, and starts to run. All it has to do is get to the first Log statement so that you know the program is running in debug mode ok.

Third thing then is to add back the Firebase module, ideally under a different name so that it only gets loaded, not actually used. See if debug mode still runs.

If it does, then start slowly changing your program over from using your dummy object to using the real Firebase, testing after each change.

If it's any consolation, I've occasionally had debug mode vanish, usually when there's a deadline looming and I'm making just one last change. But it hasn't happened to me since the B4A v9 update, so perhaps whatever that was is now fixed.

I did recently discover the hard way that running two instances* of B4A IDE makes the B4A-Bridge connection super-flakey ;-/

* accidentally and unknowingly, not on purpose
Upvote 0