Repair Flutter Deep Link Route Restore Failure

Repair Flutter Deep Link Route Restore Failure — EVIDENCE-LIMITED REVIEW

Scenario received

A deep link opens the right screen when warm but the home screen after a cold start.

Evidence inventory

• S1: Flutter router configuration — partial extract described by the requester; original full source not provided here.
• S2: incoming deep link examples — partial extract described by the requester; original full source not provided here.
• S3: restoration state traces — NOT PROVIDED; required to validate dependent findings.
• S4: app lifecycle event logs — NOT PROVIDED; required to validate dependent findings.

Case-specific checks

Compare initial route parsing. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
2.

Trace auth redirect and restoration order. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
3.

Identify repeated navigation events. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
4.

Test terminated and background states. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.

Deliverables

Route failure matrix. Create an evidence-linked section with observations, missing data, owner and next validation step.

Navigation lifecycle patch. Create an evidence-linked section with observations, missing data, owner and next validation step.

Deep link regression scenarios. Create an evidence-linked section with observations, missing data, owner and next validation step.

Acceptance gate

The fix preserves authorization guards and does not navigate users into protected screens. Do not label this gate passed until supplied source records actually demonstrate it.

Verdict and next action

INCOMPLETE — evidence required. Request S3 and S4 from the authorized owner, reconcile them with S1 and S2, then repeat the four checks and log remaining conflicts. No production change, approval, communication, or test run is claimed.