-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes get lost #130
Comments
Hello, could you show you full SDK initialisation code? Your code seems to indicated that there are some other calls between creating the config object and initialising the sdk. |
val config = CountlyConfig(this, countlyAppKey, countlyUrl)
config.setApplication(this)
config.setLoggingEnabled(true)
config.setEventQueueSizeToSend(3)
config.setUpdateSessionTimerDelay(10)
config.setIdMode(DeviceId.Type.ADVERTISING_ID)
config.setShouldIgnoreAppCrawlers(false)
config.setViewTracking(true)
config.setAutoTrackingUseShortName(true)
config.enableCrashReporting()
config.setCustomCrashSegment(mapOf(
"debug" to if (BuildConfig.DEBUG) "true" else "false",
"app_version_code" to BuildConfig.VERSION_CODE,
"devices" to sh("Main").getString("devices", "")
))
Countly.sharedInstance().init(config)
Countly.sharedInstance().requestQueueOverwriteAppKeys()
Countly.sharedInstance().crashes().addCrashBreadcrumb("App > onCreate() > init countly") |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the user is offline or server is stopped, and a crash occurs, the crash get lost!
After many tests and read the this sdk source code, i found the issue.
When an error occurs, the app stops quickly and the caching not apply..
and i solved it temporarily by adding a long run Thread.UncaughtExceptionHandler to my App.kt class, to delay the stop time
The text was updated successfully, but these errors were encountered: