◉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-08-18Advanced

The three places I had to fix before a Rork project actually targeted API level 36

My app.json said targetSdkVersion 36. The value my build actually read was 35. Here is the script that reports the effective value, and how I split my apps between raising, leaving alone, and requesting an extension.

Rork620Expo237Android66Google Play44targetSdkVersion5

✦ Premium Article

Checking thirteen days before the deadline turned out to be the right call.

Google Play starts requiring API level 36 on August 31, 2026. My Android projects already had targetSdkVersion: 36 in app.json from an earlier pass. The declaration was done, or so I assumed.

The value my build actually read was 35.

I noticed the gap while counting days left, not while checking a submission. Had I found it on submission day, I doubt I would have made it into the review queue in time. What follows is where that gap comes from, what I changed, and which apps I deliberately chose not to touch.

What changes on August 31, and what does not

The primary sources first. Skipping this step leads to fixing things that did not need fixing.

CaseRequirement from August 31, 2026
New app submissions and app updatesMust target Android 16 (API level 36) or higher
Wear OS / Android Automotive OSAndroid 15 (API level 35) or higher
Android TV / Android XRAndroid 14 (API level 34) or higher
Existing apps you are not updatingAt API level 35 or higher, they stay available to new users on devices running newer OS versions

That last row is where my decision turned.

An app you are not updating does not disappear on August 31. If it already targets API level 35, it keeps reaching new users on newer devices. What stops is the ability to submit an update. Reading this as "every app must move to 36 or distribution stops" is how you spend thirteen days on the wrong work.

There is also an extension. If you cannot make August 31, the details page of the warning on the Policy status page in Play Console opens an extension form that keeps you distributing to all Google Play users until November 1, 2026. The extension is not automatic, though. You have to file it before the deadline.

targetSdkVersion is not decided in one place

In a project generated by Rork or Expo, there are three places that can decide targetSdkVersion, as far as I could count.

  1. The expo-build-properties plugin block in app.json
  2. android.targetSdkVersion in android/gradle.properties
  3. The fallback default in the ext block of android/build.gradle

The catch is when (1) reaches (2). expo-build-properties is a config plugin that runs while npx expo prebuild generates the native directories, and the official documentation states plainly that it cannot be used in projects that do not run prebuild, meaning bare projects.

So once android/ is committed to your repository, editing app.json changes nothing until a prebuild runs. And the default in android/build.gradle is frozen at whatever SDK version the project was generated against.

In my case, I had edited app.json while reading the Expo docs, and some of those projects had already had their native directories generated. The declaration moved forward; the value the build reads stayed put. The build succeeds. Signing succeeds. You get an AAB. Nothing errors.

The more you ship generator output as-is, the more likely you are to miss this. Nothing ever gives you a reason to stop and look.

✦

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
✦Judge targetSdkVersion by the value your build actually reads, not by what app.json declares
✦Sweep every project you own with one command and know whether you will make the deadline, instead of finding out when a submission gets rejected
✦Decide per app whether to raise, leave alone, or file for an extension, using the app's own release situation
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-09-16
The Token I Deleted Came Back After a Restart — Detecting Failed SecureStore Deletes
On Android, getItemAsync can report null right after sign-out while the value is still sitting on disk. Here is how I rewrote a sign-out path that was verifying deletion by reading instead of by the delete result.
◇ App Dev2026-08-23
Bumping targetSdk to 36 surfaced a 16 KB warning. These are two different deadlines
The target API 36 deadline (August 31, extended to November 1 for those who asked) and the February 1, 2027 16 KB page size requirement are separate conditions. A dependency-free Python check for APKs and AABs, why a LOAD misalignment and a zip boundary miss need different fixes, a symptom-first troubleshooting table, and how to choose between inspection tools, checked against official docs as of November 2026.
◇ App Dev2026-11-16
I Set cameraPermission to false for a Photo Picker, and the QR Scanner Lost Its Camera Too
In expo-image-picker, cameraPermission: false deletes NSCameraUsageDescription from Info.plist on iOS and blocks CAMERA for every package on Android. Here is what happens when you also use expo-camera, and a working script that checks permissions before you submit.