Fixing the “MainActivity Not Found” Error in Android

When building Android apps in Android Studio, one of the most common issues encountered by beginners and even experienced developers is the dreaded “MainActivity not found” error. This error usually appears when you try to run your app and the IDE cannot locate the entry point for your application. While it may seem frustrating at first, resolving this issue is often straightforward if you understand its root causes.

What Causes the “MainActivity Not Found” Error?

This error can arise from a variety of misconfigurations or oversights, especially during the project setup. Below are the common reasons why Android Studio fails to locate MainActivity:

Cause	Description
Missing `<activity>` declaration	The `MainActivity` is not declared in the `AndroidManifest.xml` file.
Incorrect `intent-filter`	The app lacks the proper intent filter to mark `MainActivity` as the entry point.
Wrong package path	Android Studio expects `MainActivity` in a certain package, and it may be in another.
Class name mismatch	The actual file name or class name may differ from what’s expected.
Gradle sync issues	If your project hasn’t been synced properly, the build system may not recognize the activity.

How to Fix It

Here are several actionable steps you can take to resolve this issue:

1. Check Your AndroidManifest.xml

Ensure that your MainActivity is declared correctly and marked with the right intent filter. Your manifest should contain something like:

<activity android:name=".MainActivity">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
</activity>

2. Verify the Class Name

Double-check that your MainActivity.java or MainActivity.kt file contains the correct class name and is placed inside the appropriate package.

package com.example.myapp;

public class MainActivity extends AppCompatActivity {
    // ...
}

3. Clean and Rebuild Your Project

Go to Build > Clean Project, and then Build > Rebuild Project. This step resolves many sync-related issues.

4. Sync Gradle

If you’ve made changes to the build.gradle file, make sure to Sync Now using the prompt or the File > Sync Project with Gradle Files option.

5. Check Launch Configuration

In Run > Edit Configurations, make sure that the Launch activity is correctly set to MainActivity.

6. Use Logcat and Build Output

Always refer to the Build Output and Logcat window in Android Studio for more detailed error descriptions. These logs often point directly to the root cause.

Pro Tip: Use a Template

When creating a new activity, it’s a good practice to let Android Studio handle it via File > New > Activity > Empty Activity. This way, it auto-generates the manifest entry and intent filter, reducing manual error.

Or check our Popular Categories...

Fixing the “MainActivity Not Found” Error in Android