Bad software is everywhere, and we're tired of it. Sentry is on a mission to help developers write better software faster, so we can get back to enjoying technology. If you want to join us Check out our open positions
Current Javadocs generated from source code.
Java SDK version 1.x can still be found here.
Migration page from sentry-android 1.x and 2.x to sentry-android 4.x.
Migration page from sentry 1.x to sentry 4.x.
Releases from sentry-android 2.x and its changelogs.
Sentry Android Gradle Plugin repo sits on another repo
Adding Native support to our Android SDK.
Sample App. with Sentry Android SDK and Sentry Gradle Plugin.
Sample App. with Sentry Java SDK.
This repository includes sentry-native
as a git submodule.
To build against sentry-native
checked-out elsewhere in your file system, create a symlink sentry-android-ndk/sentry-native-local
that points to your sentry-native
directory.
For example, if you had sentry-native
checked-out in a sibling directory to this repo:
ln -s ../../sentry-native sentry-android-ndk/sentry-native-local
which will be picked up by gradle
and used instead of the git submodule.
This directory is also included in .gitignore
not to be shown as pending changes.
Installing multiple crash reporting SDKs isn't supported. They race each other on taking the signal handler (for native crashes) and it often results in only 1 of the SDKs capturing the error. This is also due to the limitations of what can run there (like allocating memory etc) and how long the app lives. This limitation also affects the Java layer, given that the operating system will kill the app before more than one SDK is able to process the crash and save the error to storage.
Since version 3.0.0 of this SDK, Sentry version >= v20.6.0 is required. This only applies to on-premise Sentry, if you are using sentry.io no action is needed.