Skip to content
Boring Doc
BreakingHigh impactOfficial migration guidesince 3.13.0windows

Migrate a Windows project to ensure the window is shown

Framework · Official source

How to update a Windows project to ensure the window is shown

Who is affected
Applications and packages relying on the previous behaviour or signature.
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.

Before and after (from the official guide)

dart+5−0
Before
1 flutter_controller_->engine()->SetNextFrameCallback([&]() {
2 this->Show();
3 });
 
 
 
 
 
After
1 flutter_controller_->engine()->SetNextFrameCallback([&]() {
2 this->Show();
3 });
4+ 
5+// Flutter can complete the first frame before the "show window" callback is
6+// registered. The following call ensures a frame is pending to ensure the
7+// window is shown. It is a no-op if the first frame hasn't completed yet.
8+flutter_controller_->ForceRedraw();
Raw before / after
flutter_controller_->engine()->SetNextFrameCallback([&]() {
  this->Show();
});
flutter_controller_->engine()->SetNextFrameCallback([&]() {
  this->Show();
});

// Flutter can complete the first frame before the "show window" callback is
// registered. The following call ensures a frame is pending to ensure the
// window is shown. It is a no-op if the first frame hasn't completed yet.
flutter_controller_->ForceRedraw();
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 (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?
Migrate a Windows project to ensure the window is shown · Boring Doc