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).
• 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 to 256 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).