Android Question Compiler always needs two attempts

[GuyBooth]

On my current "Conversion to B4XPages" project, I have a problem every time I compile my code.
When I first open B4A and compile my project, there is no problem
I change some code, then compile again. The result it this screen, after which nothing else happens - the code doesn't load into my device, and even though the buttons in the ide indicate that it is running, it is not.

When I hit the "Stop" button in the IDE and compile a second time it behaves as I expect, with this screen

This is obviously incorrect
Any thoughts? I am wondering if this is connected to another issue I am having.

 

[Erel]

Are you using a real device? B4A-Bridge or USB?

What happens if you manually launch the app after the first window?

 

[DonManfred]

B4A-Bridge or USB?

Look at the compiling-window-output ;-) (2nd Screen)
B4A-Bridge in RapidDebug

 

[Erel]

True. I guess that B4A-Bridge fails to start the app for some reason. Try to start it manually and see if it works.

 

[agraham]

Maybe lacking the 'draw over' permission. I think I have seen this when B4ABridge does not come to foreground.

 

[AnandGupta]

Maybe lacking the 'draw over' permission. I think I have seen this when B4ABridge does not come to foreground.

I have similar experience and always try to keep it foreground before compiling.

 

[GuyBooth]

I'm running a real device (Galaxy S10e) with B4A-Bridge.
I don't understand why it is saying "Running the previously successful shell app" when I have changed the code.

Today, after restarting everything, I can't reproduce the problem....

Try to start it manually and see if it works.

If the problem comes back I'll check out these other questions.

 

[Erel]

I don't understand why it is saying "Running the previously successful shell app" when I have changed the code.

The debugger is quite sophisticated and in many cases can use the same mechanism that is used for hot code swapping to rerun your project without a full compilation.
If the error returns I suggest to switch to USB debug mode.