Capacitor
Sentry's Capacitor SDK enables automatic reporting of errors, exceptions, and messages. It includes native crash support on iOS and Android.
On this page, we get you up and running with Sentry's SDK.
If you're seeing deprecation warnings in your code, please note that we're currently working on version 8 of the JavaScript SDKs. In v8, some methods and properties will be removed or renamed. Check out the Migration docs and learn how to update your code to be compatible with v8.
Don't already have an account and Sentry project established? Head over to sentry.io, then return to this page.
Sentry captures data by using an SDK within your application’s runtime.
Install the Sentry Capacitor SDK alongside the corresponding Sentry SDK for the framework you're using, such as Angular in this example:
# npm
npm install --save @sentry/capacitor @sentry/angular-ivy
# yarn
yarn add @sentry/capacitor @sentry/angular-ivy
This step is not needed if you are using Capacitor 3
Add the plugin declaration to your MainActivity.java
file
MainActivity.java
import android.os.Bundle;
import com.getcapacitor.BridgeActivity;
import com.getcapacitor.Plugin;
import io.sentry.capacitor.SentryCapacitor;
import java.util.ArrayList;
public class MainActivity extends BridgeActivity {
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
// Initializes the Bridge
this.init(savedInstanceState, new ArrayList<Class<? extends Plugin>>() {{
add(SentryCapacitor.class);
}});
}
}
Configuration should happen as early as possible in your application's lifecycle.
Then forward the init
method from the sibling Sentry SDK for the framework you use, such as Angular in this example:
app.module.ts
import * as Sentry from "@sentry/capacitor";
// Use @sentry/angular-ivy for Angular 12+ or `@sentry/angular` from Angular 10 and 11
import * as SentryAngular from "@sentry/angular-ivy";
Sentry.init(
{
dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
// Set your release version, such as "getsentry@1.0.0"
release: "my-project-name@<release-name>",
// Set your dist version, such as "1"
dist: "<dist>",
integrations: [
// Registers and configures the Tracing integration,
// which automatically instruments your application to monitor its
// performance, including custom Angular routing instrumentation
SentryAngular.browserTracingIntegration({
tracePropagationTargets: ["localhost", "https://yourserver.io/api"],
}),
],
// Set tracesSampleRate to 1.0 to capture 100%
// of transactions for performance monitoring.
// We recommend adjusting this value in production
tracesSampleRate: 1.0,
},
// Forward the init method from @sentry/angular
SentryAngular.init
);
@NgModule({
providers: [
{
provide: ErrorHandler,
// Attach the Sentry ErrorHandler
useValue: SentryAngular.createErrorHandler(),
},
{
provide: SentryAngular.TraceService,
deps: [Router],
},
{
provide: APP_INITIALIZER,
useFactory: () => () => {},
deps: [SentryAngular.TraceService],
multi: true,
},
],
})
You can also use the features available with the Sentry SDK for the framework you use, such as Angular.
You will need to upload source maps to make sense of the events you receive in Sentry.
For example, if you are using Capacitor with Ionic-Angular, upload your www
folder on every build you release. The values for <release_name>
and <dist>
must match the values passed into Sentry.init
for events to be deminified correctly.
sentry-cli releases files <release_name> upload-sourcemaps ./www --dist <dist>
Learn more about uploading source maps.
To make stack-trace information for native crashes on iOS easier to understand, you need to provide debug information to Sentry. Debug information is provided by uploading dSYM files.
Depending on how you've set up your project, the stack traces in your Sentry errors probably don't look like your actual code.
To fix this, upload your source maps to Sentry. The easiest way to do this is to use the Sentry Wizard:
npx @sentry/wizard@latest -i sourcemaps
The wizard will guide you through the following steps:
- Logging into Sentry and selecting a project
- Installing the necessary Sentry packages
- Configuring your build tool to generate and upload source maps
- Configuring your CI to upload source maps
For more information on source maps or for more options to upload them, head over to our Source Maps documentation.
This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.
import * as Sentry from "@sentry/capacitor";
Sentry.captureException("Test Captured Exception");
You can also throw an error anywhere in your application:
throw new Error(`Test Thrown Error`);
Learn more about manually capturing an error or message in our Usage documentation.
To view and resolve the recorded error, log into sentry.io and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").