Android Question Bridge not working no more on one test device of mine

[tigrot]

Hi everybody,
from today I'm getting this log debugging an app on a 5.0 Android

LogCat connected to: B4A-Bridge: LGE LG-X150
--------- beginning of system
Performing stop of activity that is not resumed: {anywheresoftware.b4a.b4abridge/anywheresoftware.b4a.b4abridge.main}
java.lang.RuntimeException: Performing stop of activity that is not resumed: {anywheresoftware.b4a.b4abridge/anywheresoftware.b4a.b4abridge.main}
at android.app.ActivityThread.performStopActivityInner(ActivityThread.java:3504)
at android.app.ActivityThread.handleStopActivity(ActivityThread.java:3593)
at android.app.ActivityThread.access$1100(ActivityThread.java:162)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1441)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:189)
at android.app.ActivityThread.main(ActivityThread.java:5535)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:950)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:745)

I saw that no log was shows and unchecking filter i saw this display.
On other devices, all with different OS, I get no problem.
Bridge release is 2.30
Compiler is 6.50

Can anybody tell me what happens.

Regards
Mauro Zanin

 

[Erel]

What exactly happens? Are you able to run B4A-Bridge?

The error above looks like an error in your app, not B4A-Bridge.
Have you tried to run a different project?

 

[tigrot]

The pjt is a little complicate, but the issue seems to be related to debug compile.(I use firebase(notifications and analytics) and fused locations). I'm able to trasfer and install the App via Bridge. Today I have time to test various combinations, I'll report to you when I'll have more info's. On other devices the App works fine. Maybe the addition of analytics broke something...

 

[Erel]

If you have access to B4A v6.80 then it is worth testing it as it can show you the unfiltered logs with B4A-Bridge (run it multiple times if it crashes on startup).

 

[tigrot]

I did initialization in starter service:

sub Service_create
analytics.Initialize
end sub

The issue was in this instruction, probably the package was not initialized at this time.

Sub Service_Start (StartingIntent As Intent)
    analytics.SendEvent("Start", CreateMap("1":"1"))
End Sub

When I took off this line everything was OK again!

Thank you
Mauro

 

[tigrot]

I was too quick: debug doesn't work for my app. I'll test the final release of 6.80, since I've not the beta. But now the App doesn't freeze any more. The issue seems to be restricted to 5.0. I'm really lucky: two issues at once!

 

[tigrot]

Al last I tried 6.80. No log except this (unfiltered):

Logger connected to:  LGE LG-X150
--------- beginning of main
[getaddrinfo]: hostname=www.xxxxxxxxxxxxxxx.it; servname=(null); cache_mode=(null), netid=0; mark=0
[getaddrinfo]: ai_addrlen=0; ai_canonname=(null); ai_flags=4; ai_family=0
[getaddrinfo]: hostname=www.xxxxxxxxxxxxxxx.it; servname=(null); cache_mode=(null), netid=0; mark=0
[getaddrinfo]: ai_addrlen=0; ai_canonname=(null); ai_flags=1024; ai_family=0
getaddrinfo: www.xxxxxxxxxxxxxx.it get result from proxy >>
[getaddrinfo]: hostname=fcm.googleapis.com; servname=(null); cache_mode=(null), netid=0; mark=0
[getaddrinfo]: ai_addrlen=0; ai_canonname=(null); ai_flags=4; ai_family=0
[getaddrinfo]: hostname=fcm.googleapis.com; servname=(null); cache_mode=(null), netid=0; mark=0
[getaddrinfo]: ai_addrlen=0; ai_canonname=(null); ai_flags=1024; ai_family=0
getaddrinfo: fcm.googleapis.com get result from proxy >>
ssl=0xb80c26f0 cert_verify_callback x509_store_ctx=0xa3c37cf8 arg=0x0
ssl=0xb80c26f0 cert_verify_callback calling verifyCertificateChain authMethod=ECDHE_RSA
sdcard state: mounted
sdcard state: mounted
sdcard state: mounted
sdcard state: mounted

No log is displayed. The APP seems to run flawlesly, but the behaviour is different from Android 4.2, on which I get lots of info.

 

[Erel]

Are you able to reproduce the crash?

 

[tigrot]

Yes, but I get no crash(at least it doesn't show any). Only debug is not shown on LGX-150. The previous crash was due to the added instruction I axplained above. Now the App starts as a bullet and do anything I need except logging. The problem seems to be restricted to Bridge.

 

[tigrot]

Tested a demo of yours(CCTV) same problem "filtered log not shown". Working fine...

 

[Erel]

Can you post the text from the logs window when you run your app in debug mode?

 

[tigrot]

CCTV (demo from your site).
On B4A 6.50:

LogCat connected to: B4A-Bridge: LGE LG-X150

Unfiltered log:

LogCat connected to: B4A-Bridge: LGE LG-X150

On B4A 6.80:

Logger connected to:  LGE LG-X150
--------- beginning of main

Unfiltered

Logger connected to:  LGE LG-X150
--------- beginning of main
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
handleMessage: 16
onFlyCompress
handleMessage: 16
handleMessage: 16
handleMessage: 16

Regards
Mauro

 

[Erel]

It is possible that /system/bin/logcat is disabled on your device or works in a non-standard way. You can switch to USB debug mode.

 

[tigrot]

Hi Erel, you solved the puzzle. The device seems not to support debugging via Wi-Fi while USB works fine. The LG X-150 proved to be not the best debugging device.