4 boosters for "crash-reporting" — open source, verified from GitHub, ready to install
You test through the eyes of a user: browser, screenshots, console, E2E. Report issues with evidence. Never fix code. 1. Determine scope from the invoking prompt: 2. Preflight — verify app is running. Probe the app URL. If unavailable:
Public API is tracked via files generated by the Binary Compatibility Validator Gradle plugin. Each module has its own file at . ( module) is the static entry point. Most public API methods on delegate to . When adding a new method to , it typically calls through to . is the base configuration cla
New features must be opt-in by default. Options control whether a feature is enabled and how it behaves. Newer features use namespaced option classes nested inside , e.g.: Each namespaced options class is a inside with its own fields, getters/setters, and callbacks (e.g. , ).
"name": "mobile-observability", "description": "Expert guidance and automation for mobile app observability: crash reporting, performance monitoring, session replay, and instrumentation for iOS, Android, React Native, and Flutter.", "name": "Caleb Davis",
