Android Question Play Console reports crashes - working fine on own device

[DaOel]

Hello!

When I want to publish my app google console reports that most of the devices are crashing in their Pre-launch report.

The Details say:

FATAL EXCEPTION: main
Process: b4a.fahrstundenPlanerSMS, PID: 20011
java.lang.RuntimeException: Object should first be initialized (Map).
    at anywheresoftware.b4a.AbsObjectWrapper.getObject(AbsObjectWrapper.java:67)
    at anywheresoftware.b4a.objects.collections.Map.getSize(Map.java:113)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice._vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv6(smsandbackupservice.java:169)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice$ResumableSub_Service_Start.resume(smsandbackupservice.java:347)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice._service_start(smsandbackupservice.java:224)
    at java.lang.reflect.Method.invoke(Native Method)
    at anywheresoftware.b4a.BA.raiseEvent2(BA.java:213)
    at anywheresoftware.b4a.BA.raiseEvent(BA.java:193)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice.handleStart(smsandbackupservice.java:100)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice.access$000(smsandbackupservice.java:8)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice$1.run(smsandbackupservice.java:71)
    at anywheresoftware.b4a.objects.ServiceHelper$StarterHelper.onStartCommand(ServiceHelper.java:237)
    at b4a.fahrstundenPlanerSMS.smsandbackupservice.onStartCommand(smsandbackupservice.java:69)
    at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3705)
    at android.app.ActivityThread.access$1600(ActivityThread.java:200)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1688)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at anywheresoftware.b4a.Msgbox.waitForMessage(Msgbox.java:248)
    at anywheresoftware.b4a.Msgbox.msgbox(Msgbox.java:187)
    at anywheresoftware.b4a.keywords.Common.Msgbox2(Common.java:452)
    at b4a.fahrstundenPlanerSMS.main$ResumableSub_Activity_Create.resume(main.java:850)
    at anywheresoftware.b4a.BA.checkAndRunWaitForEvent(BA.java:267)
    at anywheresoftware.b4a.BA.raiseEvent2(BA.java:207)
    at anywheresoftware.b4a.BA$2.run(BA.java:387)
    at android.os.Handler.handleCallback(Handler.java:873)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:193)
    at android.app.ActivityThread.main(ActivityThread.java:6718)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

I realize the line
at anywheresoftware.b4a.Msgbox.msgbox(Msgbox.java:187)
and want to mention that i am still using the old msgbox instead of the async version.

Is this the problem?
'smsandbackupservice' is a service

Does anybody understand the problem? (On my own device it works fine)

 

[rboeck]

You should initialize your map object in your service smsandbackupservice - see line 3 .

 

[DonManfred]

Usually it is helpful if you post a small project showing the problem.
Hard to help with this less informations!

 

[DaOel]

Usually it is helpful if you post a small project showing the problem.
Hard to help with this less informations!

yeah, but its hard to break it down for me. The Project is already very big

Unfortunatelly my devices do not show this error. Only most of google's Test devices have this error.
Personally I believe it is a false error by google, which will not happen on normal devices.

If you feel for it you could try on your device and search for 'FahrstundenPlaner Termi' and tell me if it crashes on start. According to google there is a 75% chance, but all my devices work with it ...

Other than this experiment, is there any tools I could use to analyse this problem.
If there is no other way I will break my code into pieces and upload it to google to check which map they are talking about...

 

[rboeck]

Try it without SMS Service, maybe it works. I installed it on my device and couldnt find any problem.

 

[DaOel]

thank you for testing.
I will add many

try
catch
end try

blocks around every Code.

Hopefully google Pre-Launch Report will be happy then.