+1
Ahhh.....what a coincidence! I have seen that message popping up occasionally and I was just sitting here thinking I need to find what causes that error-message in my app so I may handle it properly.
But now, when you mention it might be related to B4A-bridge, you made me think and as a matter of fact I never see that message using the emulator.
I think you are right and just to be sure, it would indeed be nice that the message was identified/labeled as B4A-bridge.