Android 3.0.1中默认活动未找到及Manifest文件报错求助

Hey there! I know how frustrating it is when you’ve set up your intent filter in the Manifest but still get that annoying "default activity not found" error—plus all those extra warnings cluttering up your console. Let’s break down the most reliable fixes to get your app running again:

1. Double-Check Your Manifest Intent Filter #

First, make sure your intent filter is properly structured and includes all mandatory elements. It should look exactly like this (no typos or missing tags!):

<activity
    android:name=".YourMainActivity"
    android:exported="true"> <!-- Critical for Android 12+ targets -->
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
</activity>
- Confirm the `android:name` matches your actual activity class (watch for missing dots or incorrect casing).
- If your app targets Android 12 (API 31) or higher, `android:exported="true"` is non-negotiable—omitting it will break launch functionality.

## 2. Clean & Rebuild Your Project
Stale build artifacts are a common culprit. Do this step-by-step:
- Go to `Build > Clean Project` in Android Studio.
- Once that finishes, run `Build > Rebuild Project`.
- Try launching your app again—this often clears up misaligned cached data.

## 3. Verify Your Run Configuration
Sometimes Android Studio’s run settings get misconfigured:
- Head to `Run > Edit Configurations`.
- Under your app’s `Android App` config, check the `Launch` dropdown. Ensure it’s set to `Default Activity` (or manually select your main activity if needed).
- Click `Apply` then `OK`, and test the launch again.

## 4. Invalidate Caches & Restart Android Studio
Weird IDE glitches often vanish with a cache reset:
- Go to `File > Invalidate Caches / Restart`.
- Select `Invalidate and Restart`—this clears all cached IDE data and restarts the app. It’s a go-to fix for many stubborn Android Studio issues.

## 5. Check Your Module’s Manifest Path
If your project has multiple modules, the wrong manifest might be linked:
- Right-click your app module in the Project view.
- Select `Open Module Settings` (or press F4).
- Navigate to the `Manifest File` section under `Android`—confirm the path points to your correct `AndroidManifest.xml` file.

## 6. Look for Conflicting Activities/Libraries
Third-party libraries sometimes declare their own launch activities that conflict with yours. To check:
- Go to `Build > Analyze APK`, select your app’s APK, and open the merged manifest.
- Look for multiple instances of `<category android:name="android.intent.category.LAUNCHER" />`—only your main activity should have this paired with `android.intent.action.MAIN`.

If none of these steps work, feel free to share snippets of your Manifest file and the exact error messages you’re seeing—I can help dig deeper!

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