Skip to content
Boring Doc
BreakingHigh impactOfficial migration guidesince 3.27.0landed 3.25.0-0.1.pre

Deep links flag change

Framework · Official source

What changed?

**This breaking change only affects mobile apps that use a third party deep linking plugin package.**

Will this affect my application?

Who is affected
Applications and packages relying on the previous behaviour or signature. Code that uses AndroidManifest.xml.
Practical impact
Behaviour or API differences that can break builds or change runtime behaviour.
What action should I take?
Follow the official migration guide below, update affected call sites, run `dart fix --apply` where a fix is available, then run your tests.
APIs mentioned:AndroidManifest.xml

How do I migrate safely?

Migration checklist0/4
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)

If you're using Flutter's default deep linking setup, this isn't a breaking change for you.

However, if you're using a third-party plugin for deep links, such as the following, this update introduces a breaking change:

In this case, you must manually reset the Flutter deep linking option to false.

Within your app's AndroidManifest.xml file for Android:

<manifest>
   <application
       <activity>
<meta-data android:name="flutter_deeplinking_enabled" android:value="false" />
       </activity>
   </application>
</manifest>

Within your app's info.plist file for iOS:

 <key>FlutterDeepLinkingEnabled</key>
 <false/>
Migration assistantAI-generated · grounded in cited sources
AI explanations are not configured
Set 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.

Evidence & verification

Official migration guide·Verified classification (95%)

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.

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 explanationAI-generated · grounded in cited sources
AI explanations are not configured
Set 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.
Was this useful?