H howard bassen Member Licensed User Longtime User Dec 9, 2014 #1 I cannot get the rapid debugger to work on my windows7 PC. I CAN get the legacy debugger to work. I run code (myfirstprogram.b4a) with the B4A bridge (wireless) or and emulator. Clicking on the app on my android in the data entry field allows the debugger to work with the legacy debugger but not the rapid debugger. Suggestions please?
I cannot get the rapid debugger to work on my windows7 PC. I CAN get the legacy debugger to work. I run code (myfirstprogram.b4a) with the B4A bridge (wireless) or and emulator. Clicking on the app on my android in the data entry field allows the debugger to work with the legacy debugger but not the rapid debugger. Suggestions please?
Erel B4X founder Staff member Licensed User Longtime User Dec 9, 2014 #2 Do you get any error message? Which version of B4A are you using? Upvote 0
H howard bassen Member Licensed User Longtime User Dec 10, 2014 #3 I am using v 3.82. I get no error messages. this is the compile message: Parsing code. 0.04 Compiling code. 0.18 Compiling layouts code. 0.04 Generating R file. 0.28 Compiling debugger engine code. 0.93 Compiling generated Java code. 0.85 Convert byte code - optimized dex. 0.55 Packaging files. 0.25 Copying libraries resources 0.03 Signing package file (debug key). 0.94 ZipAlign file. 0.12 Installing file to device. 4.88 Device serial: 192.168.56.101:5555 Completed successfully Upvote 0
I am using v 3.82. I get no error messages. this is the compile message: Parsing code. 0.04 Compiling code. 0.18 Compiling layouts code. 0.04 Generating R file. 0.28 Compiling debugger engine code. 0.93 Compiling generated Java code. 0.85 Convert byte code - optimized dex. 0.55 Packaging files. 0.25 Copying libraries resources 0.03 Signing package file (debug key). 0.94 ZipAlign file. 0.12 Installing file to device. 4.88 Device serial: 192.168.56.101:5555 Completed successfully
H howard bassen Member Licensed User Longtime User Dec 10, 2014 #4 I got it to debug one time after trying many operations on the emulator running the program. It is not possible to repeat this. Upvote 0
I got it to debug one time after trying many operations on the emulator running the program. It is not possible to repeat this.
Erel B4X founder Staff member Licensed User Longtime User Dec 10, 2014 #5 Does it also happen on the real device? Does it happen if you start a new project? Upvote 0
H howard bassen Member Licensed User Longtime User Dec 11, 2014 #6 You asked: Does it also happen on the real device? >>> yes I still have the problem Does it happen if you start a new project? >> yes Upvote 0
You asked: Does it also happen on the real device? >>> yes I still have the problem Does it happen if you start a new project? >> yes
Erel B4X founder Staff member Licensed User Longtime User Dec 11, 2014 #7 It is probably a network issue which prevents the rapid debugger engine (which runs on the PC) to connect to the device. If you can try to test it with USB debug mode. Upvote 0
It is probably a network issue which prevents the rapid debugger engine (which runs on the PC) to connect to the device. If you can try to test it with USB debug mode.
H howard bassen Member Licensed User Longtime User Dec 12, 2014 #8 I have already used the emulator which eliminate the network issues. This did not even work Upvote 0
