BUILT INTO EVERY GOODSPEED APP
Sentry Error Monitoring + Crash-Free SLO Gate
Sentry captures every unhandled error and performance trace in production, and a CI gate queries the Sentry Sessions API to block EAS App Store submission when the 24-hour crash-free rate drops below the configured SLO floor (default 99.5%).
- Tier: Common
- Status: Config-toggled
- Config: features.analytics.crashReporting
WHY IT MATTERS
Most mobile app projects spend weeks plumbing the same infrastructure before writing a single line of product code. Sentry Error Monitoring + Crash-Free SLO Gate is one of those cross-cutting concerns that every app eventually needs but almost none get right the first time. Permissions are handled incorrectly, tokens expire silently, or the feature breaks after an OS update nobody tested against.
Goodspeed solves this by shipping sentry error monitoring + crash-free slo gate as a production-grade, tested implementation inside every generated app. The code follows the patterns in the GAS template - the same 246-feature catalog that powers every app we build. Controlled by `features.analytics.crashReporting` in gas.config.ts. You own the code from day one, can read every line, and can hire any React Native developer to extend it. The build pipeline verifies the feature compiles and routes resolve before the app lands in your repository, so you are not the one catching the integration error at 2 am before launch.
HOW IT IS WIRED
Real code from the GAS template
The excerpt below is lifted verbatim from gas.config.ts in the gas-template repository. This is the code your generated app gets, not pseudocode, not a description of intent.
// Enable this feature in gas.config.ts
export const gasConfig = {
features: {
// Set the relevant flag to true to enable
},
};Source: goodspeed-apps/gas-template → gas.config.ts
HONEST LIMITS
When Sentry Error Monitoring + Crash-Free SLO Gate is the wrong choice
The SLO gate only applies to EAS-submitted builds; sideloaded or enterprise-distributed apps bypass it and must run the check manually. Apps with very low session volume (fewer than a few hundred sessions per day) will see high variance in the crash-free rate, making the gate unreliable as a hard block.
Tier: Common · Config-toggled
Evaluate your use case
Check whether sentry error monitoring + crash-free slo gate aligns with your target audience, platform constraints, and regulatory environment before enabling it.
Audit the config
The `features.analytics.crashReporting` flag controls this feature. Set it to false in gas.config.ts to disable the feature entirely with no residual code paths.
Seek alternatives
If the built-in implementation does not fit, the generated codebase is standard React Native + Expo code. Any library in the Expo ecosystem can replace the default.
APPS USING THIS FEATURE
Every generated Goodspeed app includes sentry error monitoring + crash-free slo gate. Browse the ideas catalog to see apps across all categories that ship with this feature wired in.
CAPABILITIES
Sentry Error Monitoring + Crash-Free SLO Gate capability breakdown
Concrete dimensions of what the built-in sentry error monitoring + crash-free slo gate implementation covers. These reflect the actual template code, not a marketing summary.
| Item | Description | Strength |
|---|---|---|
| Storage backend | Data for this feature is managed by Sentry (cloud) + Sentry Sessions API. | Sentry (cloud) + Sentry Sessions API |
| Network mode | This feature operates in Hybrid mode. | Hybrid |
| Sync frequency | Data syncs On-write + on-foreground. | On-write + on-foreground |
| Tier | Common feature — config-toggled. | Common |
| Template status | Enabled via features.analytics.crashReporting. | Config-toggled |
GET IT BUILT INTO YOUR APP