I had problems like when we switch branches, UI files like drawables, icons, xml files etc gets in android studio and caches and even after doing basic invalidate caches restart etc it didnt worked, so after compiling all steps leds to soltion , here is what I found solution with ofcourse help of gemini 3.0.

---

Issue: Persistent "Android Resource Linking Failed" (Ghost Files)

Symptoms: After switching Git branches, the build fails with Android resource linking failed pointing to XML files (e.g., fragment_loyalty_settings_new_version.xml) that do not exist in the current branch. Standard Clean Project fails or throws Permission denied errors.

Root Causes identified:

1. Gradle Cache Corruption: The Gradle Daemon held onto file references from the previous branch even after switching.

2. File Locking: Background Java processes locked the build folder, causing gradle clean to fail.

3. Permission Issues: Using sudo to delete build folders previously created root-owned files that the IDE could not overwrite.

4. Corrupt Metadata: Deleting caches while the Daemon was running caused metadata.bin (No such file) errors.

---

The "Nuclear" Fix Procedure

Perform these steps in strict order to completely reset the environment.

1. Stop Background Processes (Release Locks)

Kill all running Gradle Daemons to stop them from holding onto file locks.

./gradlew --stop

2. Fix Permission Issues (If sudo was used)

If sudo was ever used to clean, the build folder is owned by root. Force delete it using sudo one last time to clear the way.

sudo rm -rf app/build

3. Verify No "Ghost" Source Files

Ensure the file causing errors isn't actually hiding in your source code.

find . -name "fragment_loyalty_settings_new_version.xml"
# If this returns a path inside 'src', delete that file.
# If this returns nothing, the issue is purely cache/library related.

4. Wipe Project & Global Caches (Reset "The Brain")

Delete the local project cache (.gradle) and the global cache to force a metadata refresh.

# Delete local project configuration cache
rm -rf .gradle

# Delete Global Gradle cache (Optional, do only if deep corruption)
rm -rf ~/.gradle/caches/

5. Rebuild Fresh (No Daemon)

Run the build without spinning up a background daemon to ensure a clean, one-time compilation.

./gradlew clean assembleDebug --no-daemon --refresh-dependencies

If Above Didnt worked Try At Last there is Zombie Fix.

Windows Version

The "Nuclear" Fix Procedure (Windows Edition) Perform these steps in strict order to completely reset the environment on Windows.

1. Stop Background Processes (Release Locks) Kill all running Gradle Daemons to stop them from holding onto file locks. code Powershell

.\gradlew --stop

2. Force Delete Build Folder Force delete the build folder to clear the way. code Powershell

Remove-Item -Recurse -Force app\build

(If you see an error saying the item does not exist, that is fine. Ignore it.)

3. Verify No "Ghost" Source Files Ensure the file causing errors isn't actually hiding in your source code. code Powershell

Get-ChildItem -Recurse -Filter "fragment_loyalty_settings_new_version.xml"

If this returns a list of files: You must delete them manually. If this returns nothing: The issue is purely cache-related (Proceed to Step 4). 4. Wipe Project & Global Caches (Reset "The Brain") We use the cmd command here to bypass Windows "Path too long" errors. Delete local project configuration cache: code Powershell

cmd /c "rmdir /s /q .gradle"

Delete Global Gradle cache: (Note: This forces a re-download of all dependencies.) code Powershell

cmd /c "rmdir /s /q $HOME.gradle\caches"

5. Rebuild Fresh (No Daemon) Run the build without spinning up a background daemon. (I included the IPv4 flag since that helped your connection). code Powershell

.\gradlew clean assembleDebug - Djava.net.preferIPv4Stack=true --no-daemon --refresh-dependencies

When the "Nuclear" Fix Fails: The "Zombie" Folder Issue

If you have followed the steps above and are still seeing errors—specifically pointing to resource folders like layout-night or layout-v21 that shouldn't exist in your current branch—you are likely facing a Git/File System mismatch.

This happens because the folder exists locally on your disk, so Android Studio tries to merge it, even though Git isn't tracking it.

The Fix:
You need to force Git to remove untracked files and directories.

⚠️ WARNING: The command below deletes ALL files that are not committed to Git. If you have new code you haven't saved/committed yet, stash or commit it first.

Step 1: The Git Sweep
Open your terminal in the project root and run:

codeBash

git clean -fd

• -f (force): Deletes untracked files.

• -d (directory): Removes untracked directories (like that empty layout-night folder causing the crash).

Step 2: Check for specific ghost folders (Optional)
If you are paranoid about running git clean, you can manually check for the offender. Navigate to app/src/main/res/ and look for folders that shouldn't be there (e.g., layout-night). Delete them manually.

Step 3: Build without Cache
Run the build one last time, explicitly telling Gradle to ignore previous build caches.

Windows (PowerShell):

.\gradlew clean assembleDebug "-Djava.net.preferIPv4Stack=true" --no-build-cache --refresh-dependencies

Mac/Linux:

./gradlew clean assembleDebug --no-build-cache --refresh-dependencies