For apps targeting Android 17 or higher, orientation, resizability, and aspect ratio restrictions no longer apply on displays with width 600dp or greater. This means that `SystemChrome.setPreferredOrientations` is ignored on these devices.
Original behavior
Not stated in the source.
New behavior
If you rely on `SystemChrome.setPreferredOrientations` to lock your app to a specific orientation, it is ignored on large screens (widths 600dp and larger) if your app targets Android 17 or higher. If your app supports Android 16 and you did not opt out of this behavior, then it behaves the same on Android 17.
- Who is affected
- Applications and packages relying on the previous behaviour or signature. Code that uses SystemChrome.setPreferredOrientations.
- Practical impact
- Behaviour or API differences that can break builds or change runtime behaviour.
- What action should I take?
- Review the linked source, update affected code and run your test suite before upgrading.
Listed in the official breaking-changes index (docs.flutter.dev/release/breaking-changes).
An official announcement or migration guide documents an intended behaviour or API change. A verified source change (git diff) shows code changed but does not by itself prove a public API is breaking. AI interpretations are labelled and never used to classify a change.
- Official migration guide
- Android 17 behavior changes
- Android 16 behavior changes
- SystemChrome.setPreferredOrientations
- Source commit
- b3045439b7c0
- Source last updated
- Oct 21, 2026
- Last synchronized
- Oct 21, 2026
- Publication status
- published
Publication history
- Oct 21, 2026, 8:31 PM: new → published (ingestion) — Backed by an official breaking-change/migration guide.
AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.