Build fails because mipmap/ic_launcher_round is not found
AAPT: error: resource mipmap/ic_launcher_round not foundShort answer
The manifest names mipmap/ic_launcher_round, but no such file is in the res folders of the variant you build. Either generate the icons with Image Asset Studio, remove android:roundIcon (it is optional), or move the icon to the main source set so every variant sees it.
Fix it fast
1Find out which cause you have
Compare what the manifest asks for with the icon files that exist.
grep -n "icon" app/src/main/AndroidManifest.xml find app/src -path "*mipmap*" -name "ic_launcher*"2Match what you see, then jump to its fix
- 1
ic_launcher exists in the find output but ic_launcher_round does notThe round icon was never generated, or was deletedFix - 2
The manifest sets android:roundIcon but you only need one iconandroid:roundIcon is not needed and the file is goneFix - 3
find shows ic_launcher_round only under src/debug or src/releaseThe icon was generated into a debug or release folder onlyFix
- 1
What does the error look like?
AAPT: error: resource mipmap/ic_launcher_round not foundandroid:roundIcon="@mipmap/ic_launcher_round"
Cause 1 of 3
The round icon was never generated, or was deleted
1Check
Image Asset Studio creates the round icon when the Options tab has round icons enabled. A project copied from elsewhere may have only the manifest line.
find app/src -path "*mipmap*" -name "ic_launcher_round*"2Fix
In the Project window use the Android view, right-click res, choose New > Image Asset, select Launcher Icons (Adaptive and Legacy), confirm round icons in the Options tab and finish.
# New > Image Asset, then Finish: files appear in res/mipmap-<density>/3Verify
The round icon files now show in the find output; build again.
find app/src -path "*mipmap*" -name "ic_launcher_round*"
./gradlew assembleDebugConfirmed by developer.android.com
Cause 2 of 3
android:roundIcon is not needed and the file is gone
1Check
The Android docs say android:roundIcon is optional and most apps only set android:icon.
grep -n "roundIcon" app/src/main/AndroidManifest.xml2Fix
Delete the android:roundIcon attribute and keep android:icon.
<application
android:icon="@mipmap/ic_launcher"
...>3Verify
Build again.
./gradlew assembleDebugConfirmed by developer.android.com
Cause 3 of 3
The icon was generated into a debug or release folder only
1Check
Image Asset Studio asks for a resource directory. A debug or release source set applies to one build variant, while main applies to all.
find app/src -path "*mipmap*" -name "ic_launcher_round*"2Fix
Run Image Asset Studio again and pick src/main/res as the resource directory, then remove the stray copy.
# Image Asset wizard: Res Directory = src/main/res3Verify
Build the variant that failed.
./gradlew assembleReleaseConfirmed by developer.android.com
How do I stop it coming back?
- Generate icons with Image Asset Studio instead of copying manifest lines between projects.
- Keep launcher icons in src/main/res unless a variant needs a different one.
- Name resources with lowercase letters, digits and underscores only.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
Android build stops with 'resource linking failed' from AAPT2
AAPT2 aapt2-x.x.x-xxxxxxx-linux Daemon #0: Command failed
AAPT2 links your XML resources and manifest into one package, and it fails on the first thing it cannot resolve.
3 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fix