◉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/Dev Tools
⬡ Dev Tools/2026-08-21Intermediate

The four acceptance checks I still run after the build turns green

A successful build does not mean a shippable build. Here are the four failure classes an AI build loop cannot see, and a dependency-free script that inspects the artifact itself before you submit.

Rork620Expo237Android66Release5Quality

✦ Premium Article

After I shipped v2.0.0 of one of my Android wallpaper apps, the crash count in Crashlytics refused to come down. The build had never gone red. Upload passed, review passed. And yet on Android 6.0.1 devices, the app died on launch.

The cause was a Java 8 API reference without desugaring behind it, and the fix was a single line in Gradle. But the line was not the part that stayed with me. What stayed with me was finally feeling, rather than knowing, that there is a gap between "the build passes" and "this is shippable."

With Rork, where generation and building loop on the cloud side, that gap gets wider. The agent only ever sees what the compiler and linker report back. Distribution, real devices, and review sit outside its field of view.

What a green build actually guarantees

A green build guarantees roughly three things:

  1. Every type and symbol you reference exists somewhere on the compile-time classpath
  2. Resource references resolve well enough to produce a resource table
  3. The output can be packaged into a valid artifact

Everything else is unguaranteed. Classes loaded at runtime through a different path, behavior after the artifact is split for delivery, the information you need to read a crash after the fact, and files that should never have been packaged at all. Every shipping failure I have hit as an indie developer fell neatly into one of those four buckets.

CheckWhere it surfacesVisible to the build?
Missing backward compatibilityOlder OS devicesNo — runtime only
Density bucket gapsSubset of devices post-releaseNo — after splitting
Missing symbolication inputsYour crash dashboardNo — separate pipeline
Files that should not shipThe published artifactNo — packaged as instructed

Check 1: verify backward compatibility in the artifact, not the config

Desugaring settings look like something you can confirm by reading the build file. That is how I treated it at first. The case that cost me time was one where the config looked correct, but a dependency pulled in newer API references through its own path. The lesson was that the build definition is not evidence. The artifact is.

The DEX inside your artifact carries referenced class names as plain strings. When desugaring is in effect you will see rewritten names like Lj$/util/function/Supplier;. When it is not, only Ljava/util/function/Supplier; remains. Opening the artifact as a ZIP and scanning the bytes is enough to tell them apart, with no special tooling.

The symptom and the fix itself are covered in the Java 8 desugaring fix for crashes limited to older OS versions. What I want to add here is the part that catches a regression after you have fixed it once.

✦

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
✦You will be able to decide, project by project, which steps to hand to an AI build loop and which ones need a gate you own
✦You will be able to catch post-release-only failures before submission by inspecting the artifact instead of the build config
✦You will be able to move from shipping on build status alone to shipping on a four-point acceptance check
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

⬡ Dev Tools2026-10-07
Japanese Headings Won't Turn Bold on Android: How to Trace and Fix a fontWeight That Does Nothing
A troubleshooting note for Rork apps where headings look bold on iPhone but stay thin on Android. How to tell the symptoms apart, pick weights through fontFamily, and verify the fix.
⬡ Dev Tools2026-11-19
New Wallpapers Showed Up Everywhere Except the Filters: Ship the Count and the Category Lists Together
I added 67 wallpapers in one batch. They appeared in the full list and in New, but not under a single category filter, because I had raised the ID limit and forgotten to ship the category lists. Here is a pre-bump check, a client-side way to spot silent fallbacks in an Expo app, and a post-release count against the origin.
⬡ Dev Tools2026-10-30
It runs in development but the iOS Release build dies on launch — checking whether a missing scheme is the cause
In an expo-router app, an app.json with no scheme can crash only the iOS Release build at launch. Why Debug and Android survive, the two ways to fix it, how to think about leaving the scheme out on purpose, and a pre-submission check.