Crashlytics plugin
When a Mushi Mushi fix merges, writes a mushi_resolved_<reportId> flag to your
Firebase Remote Config, which your mobile app can read to stop showing a
stale crash notice. It does not create Crashlytics issues.
Not in the Mushi Mushi Cloud Marketplace yet. The console has no Crashlytics
listing, so you can’t install it from there. On a Mushi Mushi server you run
yourself, add a plugin_registry row for it and install it like any listed
plugin. To bring Crashlytics crashes into Mushi Mushi, use @mushi-mushi/adapters.
Setup (self-hosted Mushi Mushi)
npm i @mushi-mushi/plugin-crashlytics
export MUSHI_PLUGIN_SECRET=... # the signing secret set when the plugin is installed
export GCP_ACCESS_TOKEN=... # OAuth2 access token, firebase + cloud-platform scopes
export FIREBASE_PROJECT_ID=...
export FIREBASE_APP_ID=... # e.g. 1:123456789012:android:abcdef
npx -p @mushi-mushi/plugin-crashlytics mushi-plugin-crashlyticsThe plugin takes a ready access token and does not refresh it (tokens last
about an hour). Point the plugin’s webhook URL at
https://<your-host>/mushi/webhook.
Package
@mushi-mushi/plugin-crashlytics
Events
| Event | Action |
|---|---|
fix.applied | Set Remote Config mushi_resolved_<reportId> to "true" (dashes in the report id become underscores); close the Crashlytics issue only if the event carries crashlyticsIssueId (Mushi Mushi does not send it today) |
Last updated on