Navigation transactions with Navigation Integration.User interaction transactions (view click, scroll, swipe, and so on).

Performance Monitoring creates transactions for:.

User Feedback provides the ability to collect user information when an event occurs.

Attachments enrich your event by storing additional files, such as config or log files.

Release health tracks crash free users and sessions.

Navigation destination changes with Navigation Integration.

Apollo requests with Apollo Integration.

OkHttp requests with OkHttp Integration.

Android fragment lifecycle events with Fragment Integration.

User Interactions (view click, scroll, swipe, etc.).

System events (low battery, low storage space, airplane mode started, shutdown, changes of the configuration, and so forth).

Application lifecycle events (lifecycle of the application process).

Breadcrumbs automatically captured for:.

Offline caching when a device is offline we send a report once the application is restarted.

The Native Development Kit (NDK), the set of tools that that allows you to use C and C++ code with Android, is packed with the SDK.

In addition, the NDK is not only catching unhandled exceptions but is also set as a signal handler to react to signals from the OS. This process for sending a report is true if there is a fatal error in your native code as well as for the NDK. Since the environment may be unstable at the crash time, the report is guaranteed to send once the application is started again. The SDK builds a crash report that persists to disk and tries to send the report right after the crash. Sentry's Android SDK reports an error automatically whenever a thrown exception goes uncaught in your application causing the application to crash.

Error 403 github android studio