When a phone or tablet function changes with the app, network, account or location, that context is the first repair boundary. For Android default-app routing, first clear the current default for one action and choose the intended app once.
What this covers
- Android default-app routing with this exact failure state
- Diagnosis across system default versus in-app browser and domain-specific verified links
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleName the failing app, network, account or location and one context that still works. Expected behavior: open links, calls, messages and files in the intended eligible app.
Isolate the component boundary
ReversibleClear the current default for one action and choose the intended app once. Swap only that context while keeping the device, line and connection settings unchanged. Boundary to separate: system default versus in-app browser and domain-specific verified links.
Correct only the proven cause
ReversibleSet the supported default category and adjust verified-link handling. Repair the isolated permission, app profile, carrier state or network boundary.
Verify and stop safely
ReversibleRetest the previously failing and known-working mobile contexts after restart. Do not clear app data when changing a default is sufficient.
Evidence ledger
Sources behind this answer
Exact questions