Crash report - Android

  • #1, by darren-beckettMonday, 04. June 2018, 00:22 7 years ago
    Hi, I'm getting a couple of errors reported daily within Google play (pictures attached).

    - Native crash at signal 11
    - NullPointerException

    Can anyone offer any help?

    Great Poster

    384 Posts


  • #2, by wuxiaworldMonday, 04. June 2018, 04:11 7 years ago
    Very useful info, thanks addicting games

    Newbie

    1 Posts

  • #3, by NigecMonday, 04. June 2018, 20:12 7 years ago
    Native crash at signal 11 is a crash loading into memory
    NullPoint is usually something called without a value or a value -0

    All together you could be getting the null error because of the first problem

    the Native crash at signal 11 error seems common with Andriod but a bugger to fix

    Key Killer

    640 Posts

  • #4, by darren-beckettMonday, 04. June 2018, 20:24 7 years ago
    Thanks, I guess my question is...

    Can i fix this or is it the Visionaire.apk?

    Great Poster

    384 Posts

  • #5, by darren-beckettFriday, 03. August 2018, 08:25 7 years ago
    I'm still getting multiuple errors per day.

    If i knew where in the program was causing the error, i might be able to work around it.

    Could you look into building crash reporting & analytics into the android runner?

    Great Poster

    384 Posts

  • #6, by SimonSFriday, 03. August 2018, 09:34 7 years ago
    Crashing are not seldom on Android, there are enough devices so that you can't check every case. Also often Android uses some useless standby for apps, that requires the app to reload all the resources, if the App crashes then, Android will restart it.

    If there are users complaining, the reports would need to be checked.

    Thread Captain

    1593 Posts