When using the B4A bridge app (over WiFi) to work with B4A, disconnecting/disabling your WiFi on the phone/tablet causes a toast message to appear about a Java.net socket error.
While I wouldn't call this a bug, I would like to request that the toast message (assuming it is generated by the app and not something else in Android) mention the B4A Bridge.
Reason being, when testing WiFi-related stuff in your app, it can be a bit misleading as to where that message is coming from. When I was first adding the WiFi connection test to my app, I mistakenly thought this error was coming from something in my app and it took me a while to realize it was the B4A bridge app. This was of course after going nuts for about a half hour trying to figure out how to prevent the message.
I had kind of forgotten about this but was reminded again today while testing my app again.
While I wouldn't call this a bug, I would like to request that the toast message (assuming it is generated by the app and not something else in Android) mention the B4A Bridge.
Reason being, when testing WiFi-related stuff in your app, it can be a bit misleading as to where that message is coming from. When I was first adding the WiFi connection test to my app, I mistakenly thought this error was coming from something in my app and it took me a while to realize it was the B4A bridge app. This was of course after going nuts for about a half hour trying to figure out how to prevent the message.
I had kind of forgotten about this but was reminded again today while testing my app again.