Where it says app installed successfully the app has not uploaded to B4A bridge yet. The uploading bar is filled not even by the quorter of its size. Watch maximized. The phone is Samsung A41 - Android 12.
The 'app installed' message before upload is complete seems to be normal. It has done this for as long as I can remember.
As far as the timeout is concerned I guess you are saying that the debug mode doesn't wait for the full time specified before giving up, in this case about 95 seconds instead of 300. I can't comment on that as I rarely use debug mode.
The debugger connection timeout doesn't have a configuration value as far as I know and is 60s. Process Timeout is used at some other part(s) of the build, possibly when compiling Java code or a #CustomBuildAction is executed. How big is the resulting apk? Maybe you can use USB debugging if Wifi is slow.
Hi all. I have a problem. If I try to debug the app on a phone which is 3-5 years old (Android 10 Alcatel) it takes too long to install this app and the debugger stops. If I try to do the same on a phone with Android 10 LGQ-720 AM (which is more faster) - everything Ok because the same app...
Hello I have been working on an app for about 3 months and just recently it will no longer deploy with b4a bridge. Other apps I am writing do deploy to devices but this project now will not. All looks OK and the IDE seems to think its OK but the device does nothing then after exactly 60 seconds...
I may be wrong but I've always had the same experience as show in the video, debugger never waits longer than 60s. I believe I've only encountered a Process Timeout error when using a #CustomBuildAction that took a long time.
Both debug and release versions are around 22MB. Maybe this is also a good upgrade for B4A - set debugger timeout. I am opening a request in the proper forum.