Android Question Rapid Debugger Problem

[DrAlex]

Hello, I have exactly the same problem as described in

https://www.b4x.com/android/forum/threads/rapid-debugger-fails-on-every-android-device.63944.

The program runs in the release mode and in the legacy debugger, but not in the rapid debugger.

 

[DrAlex]

Yes, I did, although I don't think it is to blame, because on both computers runs the same version of the ZoneAlarm Internet Security Suite.

 

[DrAlex]

Hi Erel,

Any ideas what to check? Could it be that the device is trying to access a port on the computer that is occupied by another application?

 

[Erel]

Any ideas what to check?

Sorry but I don't have any other suggestions.

The device uses different ports each time.

 

[DrAlex]

I understand that you mean the Android ports. What about the Windows ports?

 

[Erel]

It uses several ports with several alternatives.

Have you tried the legacy debugger with B4A-Bridge?

 

[DrAlex]

Hi Erel,

The legacy debugger works fine with B4A-Bridge.

Thus we have the following situation:

Rapid - USB: Doesn't work
Rapid - B4A-Bridge: Doesn't work
Legacy - USB: Starts, but loses connection with the IDE
Legacy - B4A-Bridge: OK

 

[Erel]

As I wrote, it looks like a firewall / anti virus issue.
It prevents the internal network connections (loopback) from working so only B4A-Bridge with the legacy debugger can work.

 

[DrAlex]

Hello Erel,

I doubt that the problem is somehow related to the firewall or antivirus:

1. I have a W8 workstation and an XP laptop. Both run exactly the same version of ZoneAlarm Internet Security Suite, which includes both antivirus and the firewall. Both debuggers work fine on the XP , but not on W8.

2. I have checked the firewall and antivirus logs on W8. There is no indication that any packets were blocked.

2. If I disable both the antivirus and the firewall, the problem persists.

What else can be checked?

 

[Erel]

Sorry but I don't have any other suggestions. You should use the legacy debugger with B4A-Bridge on that computer.

 

[DrAlex]

Last question: Could you pinpoint a place in my logs, where you see that the communication failed between the device and the computer?

 

[Erel]

The fact that the legacy debugger works with B4A-Bridge and doesn't work in usb debug mode suggests that local network connections (between processes) fails on your computer.

Other than that you can see in the logs that the IDE fails to connect to the rapid debugger engine.

 

[DrAlex]

Hello Erel,

Just installed B4A v6.0 and, lo and behold, the rapid debugger started working.

Do you know why?

Anyway, thank you very much!

 

[Erel]

Did you previously set the targetSdkVersion to 23? This was not supported by previous versions of B4A.

 

[DrAlex]

No, it is set to 14.