mtjhax
commented
7 years ago Checking into this Yury... could be an auth configuration or app permissions error.
Closed y-polek closed 7 years ago
mtjhax
commented
7 years ago Checking into this Yury... could be an auth configuration or app permissions error.
y-polek
commented
7 years ago I have following permissions declared in AndroidManifest.xml:
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />Also I ensured that WRITE_EXTERNAL_STORAGE is granted before calling AppBlade.register()
y-polek
commented
7 years ago I found out that above error messages appear in log because application is not authorized (AppBlade.authorize() never called) and are not related to problem with crash reporting.
Reporting of caught exception with AppBlade.notify(ex) works fine, but uncaught exceptions are never sent to server.
I can see that exceptions are written to disk with CrashReportHelper.writeExceptionToDisk(ex) but CrashReportHelper.sendExceptionData(file) never finishes successfully (probably because application terminates before network request finishes).
In CrashReportHelper.postExceptionsToServer() I observe that number of files with saved exceptions constantly increases and never goes down.
Saved exceptions have chance to be reported only if AppBlade.notify(ex) is called without following application crash.
I thought that logged exception should be sent to server on next application launch (from AppBlade.register() or AppBlade.registerExceptionHandler()), but looks like AppBlade sends previous exceptions only when new exception is thrown.
y-polek
commented
7 years ago Seems like above problem occurs only on my device (OnePlus 2, android 6.0.1). On other devices crash reporting works fine.
Usually after crash system shows 'Crash dialog' and while it is shown background thread has chance to send crash report. On my device, for some reason, there is no 'Crash dialog' and application shuts down immediately after exception, which causes issue with sending crash report to server.
OnePlus 2 crash dialog issue: https://forums.oneplus.net/threads/android-development-oneplus-2-does-not-give-proper-crash.362323/
I've integrated AppBlade SDK in my project and registered exception handler. Problem is that crashes are not reported and I can't see them in application console.
When application starts I see "Error creating Access Token" error thrown by
AppBlade.register(this, token, secret, uuid, issuance)(see ### Log 1).Also there is some FileNotFoundException related to custom_params after test exception thrown in application (see ### Log 2)
Log 1:
Log 2: