◉RORK LABJP
●GPT-6.1 SOL — Added to Rork's model menu (09-29) with Low, Medium and High effort; included on Pro and Max●SONNET 5.5 — Claude Sonnet 5.5 is selectable: strong at UI design and faster than Sonnet 5 (09-28)●SDK 58 — Beta since 09/15 with no stable date yet; running projects in Expo Go has required login since 09/03●WIDGET — A write-up traces an iOS widget that renders black only in production builds●OBSERVE — EAS Observe now records native crashes too (SDK 57.0.21 or later, 10/07)●NEW — My App Open Ad Only Showed When the App…●GPT-6.1 SOL — Added to Rork's model menu (09-29) with Low, Medium and High effort; included on Pro and Max●SONNET 5.5 — Claude Sonnet 5.5 is selectable: strong at UI design and faster than Sonnet 5 (09-28)●SDK 58 — Beta since 09/15 with no stable date yet; running projects in Expo Go has required login since 09/03●WIDGET — A write-up traces an iOS widget that renders black only in production builds●OBSERVE — EAS Observe now records native crashes too (SDK 57.0.21 or later, 10/07)●NEW — My App Open Ad Only Showed When the App…
TAG

Sentry

7 articles
← Back to all tags
Related:
Rork4React Native3monitoring2Expo2cost optimization1Hermes1rork-max1observability1architecture1production1Crashlytics1Remote Config1
⬡ Rork Dev/2026-07-11Advanced

When Sentry Burned Through Its Event Quota in Days — Trimming Noise Before It Ships

A Sentry quota that empties early in the month is almost always a noise problem, not an error surge. Here is how to shrink event volume before it ships — with beforeSend, sampling, and grouping — while keeping the errors that actually matter inside the quota.

⬡ Rork Dev/2026-06-28Advanced

When your Rork app's production crashes arrive minified — wiring Hermes source maps and debug IDs into Sentry

Rork-generated Expo apps run on Hermes, so production crashes often arrive as index.bundle:1:284913 with no function names. Here is how to wire Hermes source maps and debug IDs into Sentry so your stack traces become readable.

⬡ Rork Dev/2026-05-22Advanced

Designing an Observability Stack for Rork Max — Unifying Sentry, Crashlytics, and Cloudflare Logs from a Solo Developer's View

A practical observability stack design for apps shipped with Rork Max, covering Sentry, Crashlytics, and Cloudflare Logs role separation, scenario-based incident tracing routes, and how a solo developer can sustain it over years.

⬡ Rork Dev/2026-05-21Advanced

Automating Production Incident Response as a Solo Developer — Crashlytics, Sentry, Slack Routing, and Staged Rollback

Twelve years of running my own iPhone and Android apps, accumulating 50 million downloads, taught me a specific shape for production incident response. This article shares the Crashlytics + Sentry double layer, Slack routing into interrupt and log channels, and a Remote Config plus EAS Update staged rollback I keep returning to.

⬡ Rork Dev/2026-05-07Intermediate

Killing the Silent Crash in Rork-Generated Apps — A Practical Error Boundary and Unhandled Promise Setup

Rork-generated code tends to swallow errors with optional chaining and leave promise rejections uncaught. Here is the minimum production-grade setup to surface those crashes instead of letting users churn in silence.

⬡ Rork Dev/2026-04-26Intermediate

App Crashes After App Store Release But Not on TestFlight — 4 Common Causes

Your Rork app worked perfectly on TestFlight, but crashes after App Store release. Here are the 4 most common causes and how to fix each one.

⬡ Rork Dev/2026-03-28Advanced

Advanced Error Handling, Debugging & Production Monitoring in Rork Max — Building Bulletproof Apps

Practical patterns for bringing production-grade resilience to Rork Max apps: layered Error Boundaries, global error handlers, structured logging, and Sentry/Crashlytics integration — plus delta-based monitoring and log-sampling lessons from running several apps in production.