◉RORK LABJP
●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30
Articles/App Dev
◇ App Dev/2026-11-12Intermediate

For the Day a Crash You Fixed Refuses to Go Away: Give Every Fix a Flag That Says It Is Active

A fix that worked in debug was silently disabled in release by code shrinking. Record whether each fix is active as a crash-report key and a log line, and confirm it on release day in an Expo Android app.

Expo237Android66R83Crashlytics14Release Verification

✦ Premium Article

A few days after shipping the version with the fix, I opened the crash list one morning. The most frequent exception was still sitting at the top. Instead of dropping, the count was slowly climbing.

This happened in the Android version of one of my wallpaper apps. An exception thrown inside the page-swiping component accounted for most of the crashes at the time. With the fix in place, I could fling through pages on a debug build on a real device as much as I liked and it never crashed.

Yet production did not improve. It was the kind of moment where you want to believe there must be another path. In reality, the fix itself had been disabled in its entirety, only in production.

Code that steps back to stay safe must always report that it stepped back. That is the line I drew most firmly from this episode. As an indie developer, I am writing it down here, translated into the setting of an Android app built with Expo.

What was actually happening

The fix replaced the "layout manager" inside the page-swiping component with a version that swallowed the exception. Because it is an internal part, there is no public way to swap it. So I located the internal field by name and replaced it through reflection.

In case the swap failed, I also added code that restored the original manager. It was an ordinary safety net, meant to keep the app from crashing.

In release builds, R8 renames classes and fields to short names. The field I was looking up by name could not be found, so the safety net kicked in and restored the original. The app did not crash. But the fix was not running either, and nothing anywhere reported that.

In debug, R8 does not run, so names stay as written. That is why the fix looked correct during on-device testing.

Stepdebugrelease
Look up the field by nameFoundNot found (the name changed)
SwapSucceedsSafety net restores the original
App behaviorException disappearsNo crash from the swap, but the same exception as before
Visible from outsideNothingNothing

The last row was the real problem. In neither build could I confirm from the outside whether the fix was in effect.

Where the same thing can happen in an Expo project

In an Expo Android project, the gap between debug and release opens the moment you enable shrinking for release. Some projects leave it off by default, so it is worth checking your own settings once.

With shrinking enabled, anything that relies on names becomes fragile:

The JavaScript side has a similar gap. Code inside if (__DEV__) is stripped from the release bundle. If you place a fix in a development-only branch, it simply does not exist in production.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦When a crash you fixed keeps showing up, you will be able to tell from the crash report's key column alone whether the fix is not running in production or the app is failing along another path
✦You can now write fail-safe code that falls back quietly for users but always reports that it fell back, so you avoid waiting weeks without knowing a fix never took effect
✦You will be able to launch a release build once on a local device and check from the log, mechanically, that every fix you shipped is active
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

◇ App Dev2026-10-27
You Changed the Environment Variable and Rebuilt for Android, but the App Still Points at the Old Server. Look at the Line That Says UP-TO-DATE
Change only an EXPO_PUBLIC_ value and rebuild a release for Android, and the bundle task can be skipped as UP-TO-DATE, leaving the old value inside. I reproduce the same behavior in a minimal Gradle project and cover how to spot it and what to do until it is fixed.
◇ App Dev2026-10-18
It Ran Fine in Debug, but the Release Build Died on Launch with a Resource Not Found. A File I Looked Up by Name Had Been Shrunk Away
A release-only crash at launch, caused by images and sounds looked up by a name string being removed by resource shrinking. A keep.xml written at prebuild, plus a post-build check that confirms it worked.
◇ App Dev2026-10-15
When Only EAS Build Fails with "No matching variant", Check Your Local android/build First
Gradle passes on your machine, but the Android build on EAS stops at "No matching variant of project". Reading the reports on GitHub, I traced how a Windows-generated autolinking cache can reach the Linux builder, and wrote a small script that checks for it before you queue a build.