Skip to content
Boring Doc
DeprecatedMedium impactOfficial migration guidesince 3.32.0landed 3.31.0-0.0.pre

Deprecate RouteTransitionRecord.markForRemove

Framework · Official source

When routes are pushed, developers can await them to be notified when they are popped. However, this didn't work when they were removed because the associated future was never completed.

Original behavior

All Navigator methods that call `remove` had this issue. By using `complete`, the issue is properly resolved, allowing developers to pass a result.

New behavior

All Navigator methods have been updated to no longer call `remove` but instead use `complete`. Context menus are now built from the `contextMenuBuilder` parameter.

Who is affected
Code that still calls the deprecated API; it keeps working until removal but produces analyzer warnings. Code that uses RouteTransitionRecord, Navigator.
Practical impact
Warnings now; removal in a future release. Plan the migration but no immediate break.
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.
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)

If you implemented RouteTransitionRecord and used markForRemove, you need to use markForComplete instead. markForRemove is now deprecated.

For other developers, no changes are required. The navigator continues to work as expected with new capabilities.

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.
Official migration guide·Verified classification (90%)

Listed in the official breaking-changes index; title states deprecation.

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?
Deprecate RouteTransitionRecord.markForRemove · Boring Doc