--- title: Android 17 (API Level 37): Everything Android Developers... description: Android 17 (API Level 37, codenamed Cinnamon Bun) released June 16, 2026, introduces breaking changes and new APIs developers must address. Key changes include... canonical: https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Android 17 (API Level 37): Everything Android Developers Need to Know | daily.dev og:description: Android 17 (API Level 37, codenamed Cinnamon Bun) released June 16, 2026, introduces breaking changes and new APIs developers must address. Key changes include... og:url: https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx og:image: https://api.daily.dev/og/posts/lHoKkvwyx.png og:image:alt: Android 17 (API Level 37): Everything Android Developers Need to Know og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Android 17 (API Level 37): Everything Android Developers Need to Know **[Medium](https://daily.dev/sources/medium_js)** · 11 min read · 17 upvotes · 2 comments ## Summary Android 17 (API Level 37, codenamed Cinnamon Bun) released June 16, 2026, introduces breaking changes and new APIs developers must address. Key changes include mandatory adaptive UI enforcement on large screens (tablets/foldables can no longer opt out of resizability), mandatory ACCESS_LOCAL_NETWORK runtime permission, a new Contact Picker replacing READ_CONTACTS, a 3-hour OTP SMS delay for targeted apps, and background audio restrictions requiring migration from ExoPlayer 2 to Media3. Under the hood, ART gains generational garbage collection, a lock-free MessageQueue implementation, and static final field modification via reflection is now blocked. New APIs include the Handoff API for multi-device state continuity, dynamic camera output surfaces, RAW14 image format, VVC (H.266) video decoding, and Encrypted Client Hello for TLS. Google Play will require API 37 targeting starting August 2027. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What happens to screenOrientation and resizeableActivity manifest attributes when targeting Android 17 API level 37 on tablets and foldables? They are ignored on devices with sw ≥ 600dp, meaning the app can no longer opt out of resizability or orientation changes and will fill the entire window regardless of manifest settings. Android 16 allowed a temporary opt-out escape hatch, but Android 17 removes it. Games with android:appCategory="game" and devices under 600dp are exempt. Developers should adopt WindowSizeClass from Jetpack WindowManager and handle onConfigurationChanged explicitly. _Teams retooling for foldables and tablets can track breaking Android API changes like this on daily.dev._ ### Is ACCESS_LOCAL_NETWORK permission required in Android 17 for apps doing mDNS or BLE discovery? Yes, for apps targeting API level 37, ACCESS_LOCAL_NETWORK enforcement is mandatory rather than optional as it was in Android 16. Any app doing mDNS browsing, raw socket connections, smart home pairing, Chromecast integration, or peer-to-peer file transfer must request the runtime permission explicitly, unless it uses system-mediated pickers like the media output switcher or NsdManager's discovery picker, which need no prompt. _Developers migrating local-network features ahead of enforcement deadlines can follow platform changes like this on daily.dev._ ### How long is the delay before an app targeting Android 17 API 37 can read an OTP SMS message via SMS_RECEIVED_ACTION? Apps targeting API 37 face a three-hour delay before OTP messages read via SMS_RECEIVED_ACTION become accessible. Exemptions apply only to default SMS apps, assistant apps, and apps already using the SMS Retriever or SMS User Consent APIs. Login flows that read SMS directly need to migrate to one of those exempt APIs to avoid stalled OTP screens. _Anyone reworking login flows before a permission deadline can watch for platform enforcement changes like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@akkitto** · 0 upvotes > I'm all for Security, but in cases like these, it's obvious, how the argument of Security is exploitable. ## Similar posts on daily.dev - [Handling the Changes That Will Actually Break Our Apps in Android 17](https://daily.dev/posts/handling-the-changes-that-will-actually-break-our-apps-in-android-17-pgotnisod) · ProAndroidDev · 0 upvotes · 0 comments - [The Second Beta of Android 17](https://daily.dev/posts/the-second-beta-of-android-17-odhr3ugeb) · Android Developers Blog · 3 upvotes · 0 comments --- Tags: [#android](https://daily.dev/tags/android) [View this post on daily.dev](https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Android 17 (API Level 37): Everything Android Developers Need to Know","url":"https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx"},"datePublished":"2026-07-02T04:51:10.069Z","dateModified":"2026-09-14T08:54:30.922Z","description":"Android 17 (API Level 37, codenamed Cinnamon Bun) released June 16, 2026, introduces breaking changes and new APIs developers must address. Key changes include...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8be484cb3d334110e323013233e25b52?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8be484cb3d334110e323013233e25b52?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":17},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"android","timeRequired":"PT11M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"Android 17 (API Level 37): Everything Android Developers Need to Know"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx","comment":[{"@type":"Comment","text":"I’m all for Security, but in cases like these, it’s obvious, how the argument of Security is exploitable.","datePublished":"2026-07-04T09:09:34.235Z","url":"https://daily.dev/posts/lHoKkvwyx#c-6Y8mXr4g6","author":{"@type":"Person","name":"Daniel","url":"https://daily.dev/akkitto","image":"https://media.daily.dev/image/upload/s--FtwJqX4c--/f_auto/v1754900041/avatars/avatar_29TCpY2hJR72V3BlxPXzX?_a=BAMClqZW0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/android-17-api-level-37-everything-android-developers-need-to-know-lhokkvwyx#faq","mainEntity":[{"@type":"Question","name":"What happens to screenOrientation and resizeableActivity manifest attributes when targeting Android 17 API level 37 on tablets and foldables?","acceptedAnswer":{"@type":"Answer","text":"They are ignored on devices with sw ≥ 600dp, meaning the app can no longer opt out of resizability or orientation changes and will fill the entire window regardless of manifest settings. Android 16 allowed a temporary opt-out escape hatch, but Android 17 removes it. Games with android:appCategory=\"game\" and devices under 600dp are exempt. Developers should adopt WindowSizeClass from Jetpack WindowManager and handle onConfigurationChanged explicitly. Teams retooling for foldables and tablets can track breaking Android API changes like this on daily.dev."}},{"@type":"Question","name":"Is ACCESS_LOCAL_NETWORK permission required in Android 17 for apps doing mDNS or BLE discovery?","acceptedAnswer":{"@type":"Answer","text":"Yes, for apps targeting API level 37, ACCESS_LOCAL_NETWORK enforcement is mandatory rather than optional as it was in Android 16. Any app doing mDNS browsing, raw socket connections, smart home pairing, Chromecast integration, or peer-to-peer file transfer must request the runtime permission explicitly, unless it uses system-mediated pickers like the media output switcher or NsdManager's discovery picker, which need no prompt. Developers migrating local-network features ahead of enforcement deadlines can follow platform changes like this on daily.dev."}},{"@type":"Question","name":"How long is the delay before an app targeting Android 17 API 37 can read an OTP SMS message via SMS_RECEIVED_ACTION?","acceptedAnswer":{"@type":"Answer","text":"Apps targeting API 37 face a three-hour delay before OTP messages read via SMS_RECEIVED_ACTION become accessible. Exemptions apply only to default SMS apps, assistant apps, and apps already using the SMS Retriever or SMS User Consent APIs. Login flows that read SMS directly need to migrate to one of those exempt APIs to avoid stalled OTP screens. Anyone reworking login flows before a permission deadline can watch for platform enforcement changes like this on daily.dev."}}]} ```