Android Studio is the official Integrated Development Environment (IDE) for Android app development. It provides tools for coding, debugging, testing, and building Android applications using Gradle. However, developers may sometimes encounter the “Module not specified” error when trying to run, build, or debug a project. As a result, Android Studio may disable the Run button, fail to create a run configuration, or prevent the project from building successfully.
This error is usually caused by a missing or corrupted Gradle configuration, an invalid run configuration, an improperly imported project, sync failures, deleted module files, or incorrect project structure. In some cases, Gradle cache corruption, plugin incompatibility, or changes to project files can also cause Android Studio to lose track of the application’s modules.
Fortunately, you can usually resolve the issue by syncing the Gradle project, recreating the run configuration, verifying the project structure, and rebuilding the project. In this guide, we’ll walk you through the most effective methods to fix the “Module Not Specified” error in Android Studio on Windows 10 and Windows 11.
How to Fix “Module Not Specified” Error in Android Studio
Before you begin, verify that your project opens without Gradle sync errors. If the project fails to sync, resolve those issues first, as Android Studio cannot detect modules correctly until the project configuration is valid.
1. Sync the Gradle Project
Gradle synchronization rebuilds the project’s module information.
- Open your project in Android Studio.
- Click Sync Project with Gradle Files.
- Wait for the sync to complete.
- Check whether the module appears in the Run configuration.
Many module-related issues are resolved after a successful Gradle sync.
2. Verify the Run Configuration
The selected run configuration may no longer reference a valid module.
- Click the Run Configuration drop-down.
- Select Edit Configurations.
- Choose your Android App configuration.
- Verify that the Module field is populated.
- Select the correct app module if necessary.
- Apply the changes.
A missing module selection is one of the most common causes of this error.
3. Recreate the Run Configuration
If the existing configuration is corrupted, create a new one.
- Open Edit Configurations.
- Delete the problematic configuration.
- Click +.
- Select Android App.
- Choose the correct module.
- Save the configuration.
A fresh configuration often resolves invalid module references.
4. Check the Project Structure
The module may not be recognized by the project.
- Open File > Project Structure.
- Select Modules.
- Verify that your app module appears.
- Check that the module has no errors.
- Apply any required corrections.
If the module is missing, it may not have been imported correctly.
5. Verify the settings.gradle File
Android Studio uses the Gradle settings file to identify project modules.
- Open the project’s settings.gradle or settings.gradle.kts file.
- Verify that your application module is included.
- Save any changes.
- Sync the project again.
If the module isn’t listed, Android Studio won’t recognize it.
6. Check the build.gradle Files
Incorrect Gradle configuration can prevent module detection.
- Open the module’s build.gradle file.
- Verify that no syntax errors exist.
- Ensure the Android plugin is configured correctly.
- Sync the project.
Gradle errors often prevent Android Studio from loading project modules.
7. Invalidate Caches and Restart
Corrupted IDE caches can cause Android Studio to lose project metadata.
- Open File.
- Select Invalidate Caches / Restart.
- Choose Invalidate and Restart.
- Wait for Android Studio to rebuild its indexes.
This clears cached project information and refreshes module detection.
8. Rebuild the Project
A clean rebuild recreates project artifacts.
- Open the Build menu.
- Select Clean Project.
- After cleaning finishes, choose Rebuild Project.
- Wait for the build to complete.
Rebuilding helps regenerate missing project metadata.
9. Delete the .idea Folder and Re-import the Project
Corrupted project configuration files may cause module problems.
- Close Android Studio.
- Delete the .idea folder.
- Reopen Android Studio.
- Import the project using the root Gradle directory.
- Allow Gradle to sync.
Android Studio recreates the project configuration automatically.
10. Update Android Studio and Gradle
Older IDE or Gradle versions may contain compatibility issues.
- Check for Android Studio updates.
- Update the Android Gradle Plugin if necessary.
- Update the Gradle Wrapper to a supported version.
- Sync the project.
Using compatible versions improves project stability.
11. Repair Corrupted System Files
Although uncommon, damaged Windows files can affect Android Studio.
- Open Command Prompt as Administrator.
- Run:
sfc /scannow
- After the scan completes, run:
DISM /Online /Cleanup-Image /RestoreHealth
- Restart your computer.
These tools repair Windows components that applications depend on.
12. Clone or Restore the Project Again
If important project files have been deleted or corrupted, restoring a clean copy may be the fastest solution.
- Clone the project from your version control system.
- Or restore it from a backup.
- Open the project in Android Studio.
- Allow Gradle to sync completely.
- Verify that the module appears.
A fresh copy eliminates issues caused by damaged project files.
Conclusion
The “Module Not Specified” error in Android Studio is usually caused by invalid run configurations, Gradle sync failures, corrupted project metadata, or incorrect project structure. In most cases, syncing the Gradle project, recreating the run configuration, verifying the settings.gradle file, and rebuilding the project will resolve the issue.
If the error persists, invalidate Android Studio’s caches, delete the .idea folder, update Android Studio and Gradle, or restore a clean copy of the project. Maintaining a properly synchronized Gradle project and using version control will help prevent similar module configuration errors in the future.
