Android 17: lock-free MessageQueue and static final fields
Short answer: apps that target Android 17 (API level 37) get a new lock-free implementation of android.os.MessageQueue, which Google says improves performance and reduces missed frames but breaks code that reflects on its private fields and methods. The same target also makes static final fields unmodifiable: changing one through reflection throws IllegalAccessException, and through JNI it crashes the app. Both changes hit apps and libraries that rely on reflection, including older test frameworks.
What to update
From Android Developers’ Android 17 behavior changes and MessageQueue guidance, read 1 October 2026.
| If you use | What changes at target 37 | What to do |
|---|---|---|
| Reflection on MessageQueue, e.g. mMessages | mMessages stays but is always null | Stop inspecting MessageQueue internals |
| Espresso | Older versions relied on MessageQueue reflection | Update to Espresso 3.7.0 or newer |
| Robolectric | Legacy Looper mode is affected | Update to Robolectric 4.17 or newer; move LooperMode LEGACY to PAUSED |
| Reflection that writes static final fields | Throws IllegalAccessException | Stop writing to static final fields |
| JNI calls such as SetStaticLongField on a static final field | The app crashes | Remove the write |
Why MessageQueue changed
Since the first Android release,
MessageQueue used a single lock to manage the main thread’s task queue, so a background thread could block the main thread and cause dropped frames. Android 17 rewrites the class underneath Looper and Handler without that lock. To keep binary compatibility the private mMessages field still exists, but in the new implementation it is always null, whether or not messages are queued, so any code that reads it to peek at pending messages silently gets the wrong answer.Test frameworks
Espresso needs to know when the main thread is idle, and earlier versions found out through reflection. Espresso 3.7.0 and newer use the
TestLooperManager API, including APIs added in Android 16, instead. If you run unit tests with Robolectric, update to Robolectric 4.17 or newer and migrate tests from @LooperMode(LEGACY) to @LooperMode(PAUSED), following Robolectric’s migration guide.Testing and switching it off
You can try the new queue before changing your target SDK: on a debuggable build, run
adb am compat enable USE_NEW_MESSAGEQUEUE <your-package-name>. Once you target API level 37 it is on by default. If you see crashes or odd behavior, turn it off temporarily with adb am compat disable USE_NEW_MESSAGEQUEUE <your-package-name> or in App Compatibility Changes in Developer Options, which restores the lock-based queue so you can confirm whether MessageQueue is the cause.Other Android 17 changes
The full list is in Android 17 behavior changes. Raising your target to 37 brings more changes at once: certificate transparency by default, the local network permission and background audio hardening. For when Google Play will require it, see Google Play target API level.
Where Censuus fits
Fewer dropped frames keep users around; being found brings them. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.
Frequently asked questions
What changed in MessageQueue in Android 17?
Apps targeting Android 17 (API level 37) get a new lock-free implementation of android.os.MessageQueue. It improves performance and reduces missed frames but breaks code that reflects on MessageQueue private fields and methods.
Why is MessageQueue.mMessages null on Android 17?
The field is kept only for binary compatibility. In the new lock-free implementation it is always null, whether or not there are messages in the queue.
Which Espresso and Robolectric versions work with Android 17?
Espresso 3.7.0 or newer and Robolectric 4.17 or newer. Robolectric tests using LooperMode LEGACY need to move to LooperMode PAUSED.
How do I turn off the new MessageQueue for testing?
Run adb am compat disable USE_NEW_MESSAGEQUEUE with your package name, or use App Compatibility Changes in Developer Options.
Can I still change static final fields with reflection on Android 17?
No, if your app targets Android 17. Reflection throws IllegalAccessException, and modifying the field through JNI, such as SetStaticLongField, crashes the app.
Guides for app developers
- How to market an app: a stage-by-stage plan
- Submit your app for free
- How to get your app to show up in Google search
- How to get your app recommended by AI assistants
- Free app promotion sites, checked for dofollow
- App store optimization checklist: what Apple and Google actually say
- App launch checklist: iOS and Android, step by step
- How to find beta testers for your app
- How to get more app reviews without breaking the store rules
- How to get your app featured on the App Store and Google Play
- App Store and Google Play screenshot sizes: what you must upload
- How to promote an app on Google Play with Play Console’s own tools
- How to promote an iOS app with App Store Connect’s own tools
- App Store keywords: how to fill the 100-character field
- How to market a fitness app: what Apple and Google let you claim
- How to market a kids app: the store rules that shape it
- How to market a finance app: the store rules to know first
- How to market a dating app: the store rules that shape it
- How to market a subscription app: what the stores require of your offer
- How to market a mobile game: the store rules that shape it
- Apple Ads MCP: connect an AI assistant to your campaigns
- How to promote an app on TikTok with creators
- How to promote an app on YouTube with creators
- How to market a VPN app: the store rules to know first
- How to market an AI app: the store rules that shape it
- How to market an education app: schools, parents and learners
- How to localize your App Store and Google Play listing
- Android vitals and Google Play visibility: the thresholds that hide apps
- App Store and Google Play age ratings: what drives them
- App Store privacy labels and Google Play Data safety: what to declare
- Common App Store rejection reasons and how to avoid them
- How to get the first users for your app
- App preview video specs: App Store sizes, length and rules, and the Google Play video
- App Store custom product pages, and the Google Play version
- App icon size for the App Store and Google Play
- App Store phased release and Google Play staged rollouts
- App Store subtitle and promotional text: limits and how to use them
- Google Play feature graphic: size, placement and rules
- TestFlight public link: set it up, limit it, and fix it when it does not work
- App Store promo codes and offer codes: how they work and their limits
- App Store A/B testing: product page optimization and Google Play experiments
- App Store in-app events: limits, badges and media sizes
- App Store Connect analytics: what each metric means
- Google Play store listing reports: clicks, CTR and the 2026 changes
- Google Play target API level requirements for 2026
- Android developer verification: what changed on September 30, 2026
- App Store and Google Play fees in 2026
- Google Play’s 12 testers for 14 days rule, explained
- How to transfer an app to another developer account
- How to remove an app from the App Store and Google Play
- The app account deletion requirement on the App Store and Google Play
- Google Play 16 KB page size requirement: dates, checks and fixes
- Declared Age Range and Play Age Signals: age assurance APIs for app developers
- Xcode 26 and the iOS 26 SDK requirement for App Store Connect
- The iOS privacy manifest: what to declare and how
- Accessibility Nutrition Labels: what to declare on your App Store page
- Google Play’s photo and video permissions policy, explained
- Google Play Billing Library version requirement: what you need to ship now
- App Tracking Transparency: when to ask and how
- App Store Connect API key: create it, store it, use it
- How to submit an In-App Purchase for review
- The Play Integrity API: what it checks and how to use it
- How long app review takes on the App Store and Google Play
- Google Play policy updates in 2026, with the deadlines
- Rosetta 2 end of support: what Mac developers need to do
- Monthly subscriptions with a 12-month commitment on the App Store
- Subscription Bundles, Suites and multiseat purchases on the App Store
- Sign in with Apple private relay email and the new private.icloud.com domain
- App Store Server Notifications V2: switching from V1 and handling every event
- Migrating to StoreKit 2: what is deprecated and what replaces it
- App Store creative assets: headers and search result visuals in iOS 27
- On-Demand Resources is deprecated: moving to Background Assets
- Time Allowances in iOS 27: how your app gets its category
- Android Contact Picker and the new READ_CONTACTS rules
- The Android 17 location button and Google Play’s precise location rules
- Phone verification without READ_CALL_LOG: what replaces call-based checks
- Apple’s EU business terms from October 1, 2026
- Android 17 app memory limits: detect, test and stay under them
- The Android 17 local network permission
- Android 17 background audio hardening
- Cleartext HTTP and certificate transparency on Android 17
- Android 17 ignores orientation lock and resizability on large screens
- Android 17 behavior changes: a checklist for target SDK 37
- Preparing your app for iPhone Duo
- Google Play subscription grace period and account hold
- Getting your Android app ready for Googlebook
- The Android 17 Handoff API
- ADB Wi-Fi 2.0 wireless debugging
- Android AppFunctions: your app as on-device tools for AI agents
- Android Live Updates: how to qualify for a promoted notification
- App Store Connect webhooks
- Apple Foundation Models: on-device vs Private Cloud Compute
- Using Claude, Codex and other agents in Android Studio
- Gemini Nano for Android developers
- Firebase AI Logic: the App Check deadline and Gemini 2.5 shutdowns
- Swift 6.4: what’s new for app developers
- The Swift SDK for Android
- Publishing your game on Android Auto and Android Automotive OS
- Liquid Glass in a Compose Multiplatform app
- Expo SDK 58: when it ships and what changes
- Device Hub in Xcode 27
- Using the Xcode MCP server with Claude Code, Codex and other agents
- Xcode 27: release, requirements and point releases
- Gemma 4 and Android skills in Android Studio
- The UIScene life cycle is required in iOS 27
- Migrating to Android Gradle plugin 9
- Navigation 3 for Jetpack Compose
- Kotlin 2.4, 2.4.20 and the road to 2.5
- Upgrading your app build to Gradle 9
- The latest Compose BOM and Compose 1.12
- Compose Multiplatform 1.12 and the Hot Reload MCP server
- Opting out of Liquid Glass with UIDesignRequiresCompatibility
- Flutter 3.47 and the latest stable version
- React Native 0.87 and the latest version
- Android Studio Quail 4 and what comes next
- CocoaPods goes read-only: what changes and when
- Fixing YouTube Error 153 in embedded players
- Fixing “APNS token has not been set yet” in Firebase Messaging
- Older iOS Simulator runtimes and Rosetta destinations in Xcode
- Fixing the fmt consteval error in React Native on Xcode 26.4
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.