5f1a0548f5
Summary: Docusaurus 2 is quite a lot more powerful than docu 1 it turns out. This should convert the website fully. * [done] Go through migration guide https://v2.docusaurus.io/docs/migrating-from-v1-to-v2 * [done] Convert landing page html * [done] Convert all images to img tags * [done] Convert all .md files to .mdx * [done] Make sure ui-doc generation and including still works * [done] Scan every page visually for sanity check * [done] Make sure footer still works * [done] Make sure search still works * [done] Change all links/ to links/index * [done] Change all links.md to links * [done] Add some custom css to make the navbar look like the old one and darken the footer. Reviewed By: passy Differential Revision: D21158717 fbshipit-source-id: 5f45b711b1b6fd5ece4c5c15c55635c7ebbfb568
24 lines
1022 B
Plaintext
24 lines
1022 B
Plaintext
---
|
|
id: crash-reporter-plugin
|
|
title: Crash Reporter Setup
|
|
sidebar_label: Crash Reporter
|
|
---
|
|
|
|
You do not have to instantiate it in your app in order to use its basic functionality mentioned [here](features/crash-reporter-plugin). You can also use crash reporter plugin to send the notifications for the exception which you suppress in your Android application. You could even use it to send the notifications when the [Litho Error Boundary](https://fblitho.com/docs/error-boundaries) is triggered. In order to send your custom notification you will have to follow the following steps.
|
|
|
|
## Android
|
|
|
|
Instantiate and add the plugin in `FlipperClient`.
|
|
```java
|
|
import com.facebook.flipper.plugins.crashreporter.CrashReporterPlugin;
|
|
|
|
client.addPlugin(CrashReporterPlugin.getInstance());
|
|
```
|
|
|
|
Use the following API to trigger your custom crash notification.
|
|
|
|
```java
|
|
import com.facebook.flipper.plugins.crashreporter.CrashReporterPlugin;
|
|
CrashReporterPlugin.getInstance().sendExceptionMessage(Thread.currentThread(), error);
|
|
```
|