Releases: microsoft/appcenter-sdk-android
Releases · microsoft/appcenter-sdk-android
0.4.0
- Most of the crash processing is now happening on a background thread when the application restarts, solving multiple strict mode policy issues.
- As a consequence, the
getLastSessionCrashReport
is now an asynchronous function with a callback (breaking change).
- As a consequence, the
- Fix Proguard configuration inside the main AAR file, no Proguard configuration required on application side.
- Fix a race condition crash inside HTTP channel management when counting pending logs.
- Fix other race conditions in HTTP channel management that could lead to inconsistent behavior.
- Fix crash when the default ASyncTask thread pool is saturated when sending HTTP logs (now retries later).
StackOverflowError
throwable object for client side inspection is now truncated to256
frames.- App secret is now obfuscated in logs when setting verbose log level.
- Threads where crash callbacks are executed is now documented with the support annotations and the behavior is now consistent (either always UI thread or always worker thread depending on the callback).
0.3.3
- Fix a bug where
CrashesListener.onBeforeSending
orCrashesListener.onSendingFailed
could not be called. - Truncate
StackOverFlowError
to 256 frames (128 at start and 128 at end) to allow them being reported. - Retry more https errors due to transient ssl failures when the client or server connectivity is bad.
- On crash, wait 5 seconds for local storage to flush other pending events to disk so that they are not lost.
0.3.2
0.3.1
0.3.0
0.2.0
- Rename Sonoma to MobileCenter.
- Fix a bug that caused crashes to be sent twice if calling Crashes.setEnabled(true) while already enabled.
- New logs in assert level for successful SDK initialization or failed to initialize.
- Allow wrapper SDKs such as Xamarin to label an exception as being generated by the wrapper SDK.