Resolving Android Studio Not Installed Warning in Flutter Doctor on macOS

Problem Context and Analysis

Flutter developers working on macOS often encounter a puzzling situation: even when Android Studio is successfully installed and fully functional, running the flutter doctor command still displays an Android Studio (not installed) warning. This apparent contradiction actually reflects the specific detection mechanism of the Flutter toolchain for IDE installation paths.

Root Cause Investigation

Flutter Doctor verifies Android Studio presence by checking standard system installation paths. In macOS systems, the standard application installation location is the /Applications folder. When users run Android Studio directly from downloaded DMG files without dragging it to the Applications folder, Flutter Doctor cannot locate the IDE at the expected location, thus reporting it as not installed.

This situation doesn't affect basic development functionality since the Android toolchain (SDK, platform tools, etc.) is properly configured. However, the lack of IDE detection may impact the availability of some advanced features, particularly those related to Flutter and Dart plugins.

Solution Implementation

Based on community-verified best practices, the most direct solution to this problem is to properly move the Android Studio application to the system Applications folder:

1. First ensure Android Studio is completely closed
2. Open Finder and navigate to the current Android Studio location
3. Drag the Android Studio application icon to the /Applications folder
4. Wait for the file copy to complete
5. Re-run the flutter doctor command

After completing these steps, Flutter Doctor should correctly recognize Android Studio's installation status, and the corresponding warning message should disappear. This process ensures the IDE is located at the system standard position, allowing the Flutter toolchain to discover its presence through conventional detection mechanisms.

Technical Principles Deep Dive

Flutter Doctor's detection logic is based on predefined path search patterns. In macOS systems, it primarily checks the following locations:

// Core path checking logic for Android Studio detection in Flutter
const List<String> macOSPaths = [
  '/Applications/Android Studio.app',
  '/Users/*/Applications/Android Studio.app'
];

When Android Studio is not in these predefined paths, the detection mechanism fails. This design ensures detection reliability but also requires developers to follow standard software installation practices.

Cross-Platform Solution Comparison

While this article focuses on macOS solutions, understanding approaches for other operating systems helps comprehensively grasp the problem essence:

Windows Environment

In Windows systems, you can specify Android Studio's installation directory through configuration commands:

flutter config --android-studio-dir="C:\Program Files\Android\Android Studio"

This method directly informs the Flutter toolchain of the IDE's exact location, bypassing the automatic detection mechanism.

Linux Environment

Linux users need different configuration methods depending on their installation approach. For snap installations:

flutter config --android-studio-dir="/snap/android-studio/current/android-studio"

For installations via JetBrains Toolbox:

flutter config --android-studio-dir=/home/myuser/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882

Verification and Next Steps

After implementing the solution, it's recommended to run detailed diagnostic commands for verification:

flutter doctor -v

This command provides more detailed output information, including specific path detection results and plugin status. If Android Studio detection succeeds but still shows plugins as not installed, follow the prompts to install Flutter and Dart plugins for a complete development experience.

Best Practices Recommendations

To avoid similar issues, developers are advised to always follow standard procedures when installing Android Studio:

• After downloading official DMG files, drag the application to the Applications folder
• Avoid running the IDE from temporary locations
• Regularly update Flutter SDK to ensure detection logic compatibility
• Standardize IDE installation practices in team development environments

By following these best practices, you can ensure development environment stability and consistency, reducing the occurrence of configuration problems.