what extra insight will Crashlytics give me

Corona Marketplace Corona Community Plugins
#1

Hi,

I was wondering what the added value will be when I start using Crashlytics.

In the google developer tool I see logs for ANR and Crashes like below:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)    liblua.so

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)    in libopenal.so

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)    in lua_getinfo

Executing service com.pijappi.logibraingrids/shared.google.play.services.base.PackageStateChangedService

Besides that I also see errors in Google Analytics like:

/Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:167: attempt to index a nil value stack traceback: /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:167: in function ‘hasEventListener’ /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:216: in function </Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:190>

/Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:8388638: attempt to stack traceback: /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:8388638: in function </Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:190>

/Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:184: bad argument #2 to ‘(for generator)’ (number expected, got table) stack traceback: [C]: in function ‘(for generator)’ /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:184: in function ‘cloneArray’ /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:213: in function </Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:190>

I’m wondering if Crashlytics will give me the extra information I’m looking for to fix those ANR’s/crashes. Or will it still be the same cryptic log texts as I currently see, which are not very useful for when attempting to fix them.

#2

I have crashlytics setup to catch lua errors. https://docs.coronalabs.com/native/ios/index.html#custom-lua-error-handling

I don’t know if that will help too much.

#3

Thanks Scott,

I think the only way to find out is to start using Crashlytics then :wink:

Will see if i have this week to implement it into my apps

#4

I know this is an old thread but just wondering if you got anywhere with this?

#5

No did not implement it into my apps. The issues that occured most (see below) are Corona related and out of my reach

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)    liblua.so

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)    in libopenal.so

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)    in lua_getinfo

Executing service com.pijappi.logibraingrids/shared.google.play.services.base.PackageStateChangedService