如何将PDF阅读器注册为PDF文件隐式意图？排查未显示问题

Hey there! Let's figure out why your custom PDF reader isn't showing up in the open-with list when you tap a PDF file. First, could you share the exact <intent-filter> section (plus the surrounding Activity declaration) from your AndroidManifest.xml? That’ll help spot exactly where things might be going wrong.

In the meantime, here are the most common pitfalls that cause this issue, along with the correct setup to fix them:

1. Missing critical intent components #

Your intent filter must include both ACTION_VIEW and CATEGORY_DEFAULT—without CATEGORY_DEFAULT, Android won’t even consider your app for implicit intents like opening a file. You also need to declare the right MIME type for PDFs.

2. Not handling all URI schemes #

Lots of modern file managers use content:// URIs instead of the old file:// ones. If your filter only handles one scheme, your app might get skipped entirely.

Working intent filter template #

Here’s a solid example to compare your code against:

<activity
    android:name=".YourPDFReaderActivity"
    android:exported="true"> <!-- Mandatory for Android 12+; good practice for all versions -->
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" /> <!-- Optional, lets your app open PDFs from browsers -->
        
        <!-- Target PDF MIME type -->
        <data android:mimeType="application/pdf" />
        
        <!-- Support file:// URIs -->
        <data android:scheme="file" />
        
        <!-- Support content:// URIs (from media store, cloud file managers) -->
        <data android:scheme="content" />
    </intent-filter>
</activity>

Quick checks to run right now: #

• Double-check that android:exported="true" is set on your Activity. If your app targets Android 12 or higher, this is non-negotiable—without it, your app won’t receive implicit intents.
• Make sure your MIME type is spelled exactly application/pdf (no typos like extra spaces or wrong capitalization!).
• If you split <data> elements into separate tags, ensure they’re all in the same intent filter. Each <data> tag adds constraints, so mixing schemes and MIME types across filters can break the matching logic.

Once you share your actual manifest code, we can pinpoint the exact issue and fix it up!

内容的提问来源于stack exchange，提问作者cardaguh