Android Question Crash

[aaronk]

Hi,

Noticed Google Play has now updated and now has a Android Vitals, which is a new way in detecting crashes etc. I noticed a few crashes for one of my apps, but can't work out where this error is happening.

Crash 1:
(all 3 pages are the same)

java.io.EOFException
anywheresoftware.b4a.shell.Shell.raiseEventImpl

I am guessing this crash is some timer which caused the crash, but not sure which one?

Crash 2:

java.net.SocketException
anywheresoftware.b4a.shell.ShellConnector.sendControlMessage

I am guessing this was caused by sending data out of the socket? But not sure what caused it? (maybe the socket was closed while it sent the data?

Is there a way to find out what line of code caused the errors or know what function in the app caused it so I can begin troubleshooting the crashs ?

 

[Erel]

You have uploaded a debug APK to the store.

 

[aaronk]

You have uploaded a debug APK to the store.

I ran the app as 'Release (obfuscated)' and then got the apk file from the objects folder and uploaded that to Google Play. (unless this is not what I should of done and I should be doing this differently?)

I downloaded the APK from the Google Play Console (the one which I uploaded), is there a way in seeing if it was a debug or release apk file (in case I did upload the wrong file)

 

[Erel]

I ran the app as 'Release (obfuscated)' and then got the apk file from the objects folder and uploaded that to Google Play.

This is the correct way. However from the stack trace we can see that it is a debug APK. ShellBA is part of the debug library.

You can use the dex2jar tool to decompile the APK and then see whether the debug classes are included.

 

[aaronk]

After I used dex2jar I then used JD Project which allowed me to view the code of the jar file.

I am guessing one of these is the debug ?

 

[Erel]

Open the debug node.

 

[tigrot]

Some month ago i sent to Google Play a debug version and it refuses to load and asked a new version. Seems they distinguish it.

 

[aaronk]

Open the debug node.

 

[Erel]

This is a release APK.

I guess that the stack trace is coming from a different APK. You can see that there is no anywheresoftware.b4a.shell package in the APK.

 

[aaronk]

I am about to release another update and will double check make sure it's the release version I upload, and will monitor it and see if this one comes back with any crashes.