I’ve dealt with this exact conflict between Windows Android Studio and WSL Bash before—here’s a step-by-step fix to get both environments working smoothly without having to manually delete local.properties every time:

1. Make Gradle prioritize ANDROID_HOME over local.properties #

Android Studio generates local.properties because Gradle defaults to looking for SDK paths there if the file doesn’t exist. We can override this by forcing Gradle to pull the SDK path directly from your environment variables.

• Open your project-level build.gradle (the one in the root of your project, not the module-specific one) and add this at the very top:

  // Pull SDK path from environment variables first
  def androidSdkPath = System.getenv("ANDROID_HOME") ?: System.getenv("ANDROID_SDK_ROOT")
  if (androidSdkPath != null) {
      project.ext.set("androidSdkPath", androidSdkPath)
  }
  

• Then open your module-level build.gradle (usually in app/build.gradle) and update the android block to use this variable instead of relying on sdk.dir:

  android {
      compileSdkVersion 34 // Replace with your target SDK version
      buildToolsVersion "34.0.0" // Replace with your build tools version
  
      // Use SDK path from environment variable
      if (project.hasProperty("androidSdkPath")) {
          sdkDir = file(project.androidSdkPath)
      }
  }
  

2. Prevent Android Studio from auto-generating local.properties #

Android Studio will only create local.properties if the file doesn’t exist. So we’ll create a placeholder version to block auto-generation:

• In your project root, create a file named local.properties and add only this comment (no sdk.dir line):

  # Placeholder file to stop Android Studio from auto-generating SDK path
  # SDK location is loaded from ANDROID_HOME environment variable
  

  This tells Studio the file exists, so it won’t overwrite it with a Windows-formatted path.

3. Configure ANDROID_HOME for both Windows and WSL Bash #

You’ll need to set the environment variable in both environments, using the correct path format for each:

Windows setup: #

1. Right-click This PC → Properties → Advanced system settings → Environment Variables.
2. Under System variables, click New and add:
   • Variable name: ANDROID_HOME
   • Variable value: C:\Users\me\Android SDK (use your actual SDK path)
3. (Optional) Add ANDROID_SDK_ROOT with the same value—some tools prefer this variable over ANDROID_HOME.
4. Click OK to save changes, then restart Android Studio to pick up the new variable.

WSL Bash setup: #

1. Open your shell config file (e.g., ~/.bashrc for Bash, ~/.zshrc for Zsh) in a text editor:

   nano ~/.bashrc
   

2. Add these lines at the bottom, replacing the path with your WSL-formatted SDK location:

   export ANDROID_HOME="/mnt/c/Users/me/Android SDK"
   # Add SDK tools to PATH for easy command access
   export PATH="$ANDROID_HOME/platform-tools:$ANDROID_HOME/tools:$PATH"
   

3. Save and close the file, then reload the config to apply changes:

   source ~/.bashrc
   

4. Verify everything works #

• Restart Android Studio and open your project—check that no new local.properties is generated (only your placeholder version exists).
• In WSL Bash, navigate to your project directory and run a basic Gradle command to confirm the SDK is found:

  ./gradlew tasks
  

  If this runs without path errors, your setup is working.

内容的提问来源于stack exchange，提问作者Denys Kniazhev-Support Ukraine