ActivityNotFoundException: Resolve the Intent and Provide a Fallback

Distinguish explicit and implicit intents

An explicit intent names a component; an implicit intent describes an action and optional data/type. Check the exact values before adding manifest filters randomly.

The manifest reference explains component declarations. A misspelled class name or component excluded from the selected build variant cannot be repaired by changing the caller's MIME type.

Verify the requested capability

Use a real supported test target and also test a device without that target installed.

Account for package visibility

Android package visibility can affect queries about installed handlers. A query result and the ability to attempt an activity launch are related but not identical APIs; follow the documented rules for the operation.

Do not request broad package visibility merely to avoid understanding a narrow intent contract.

Provide a safe fallback

Catch the launch failure at the user-action boundary and offer a meaningful alternative, such as choosing another supported app or explaining that no compatible handler is available.

Avoid silently losing a file or leaving a disabled button after the failed launch. Keep any temporary URI permission limited to the intended recipient and operation.

Test installed and missing-handler states

APKLint's Manifest Checker can inspect declared components and filters, but it cannot know which apps are installed on a user's device. The acceptance test must include the exact intent on relevant devices, including the no-handler case and the selected release variant.