Android resource linking failed

Question

does anyone know what is this error and how can I fix this? I am trying to open a source code from Mumble and stucked with this error

Android resource linking failed
Output:  C:\Users\NP\Desktop\Plumble-Legacy-master\build\intermediates\incremental\mergeDebugResources\merged.dir\values\values.xml:352: error: resource android:attr/popupPromptView is private.
error: failed linking references.

Command: C:\Users\NP\.gradle\caches\transforms-1\files-1.1\aapt2-3.2.0-alpha17-4804415-windows.jar\1d0ef7dbf7bb928283477115487f45e4\aapt2-3.2.0-alpha17-4804415-windows\aapt2.exe link -I\
    C:\dev\sdk\android-sdk-essential-3.1.3\platforms\android-27\android.jar\
    --manifest\
    C:\Users\NP\Desktop\Plumble-Legacy-master\build\intermediates\merged_manifests\debug\processDebugManifest\merged\AndroidManifest.xml\
    -o\
    C:\Users\NP\Desktop\Plumble-Legacy-master\build\intermediates\processed_res\debug\processDebugResources\out\resources-debug.ap_\
    -R\
    @C:\Users\NP\Desktop\Plumble-Legacy-master\build\intermediates\incremental\processDebugResources\resources-list-for-resources-debug.ap_.txt\
    --auto-add-overlay\
    --java\
    C:\Users\NP\Desktop\Plumble-Legacy-master\build\generated\not_namespaced_r_class_sources\debug\processDebugResources\r\
    --custom-package\
    com.morlunk.mumbleclient\
    -0\
    apk\
    --output-text-symbols\
    C:\Users\NP\Desktop\Plumble-Legacy-master\build\intermediates\symbols\debug\R.txt\
    --no-version-vectors
Daemon:  AAPT2 aapt2-3.2.0-alpha17-4804415-windows Daemon #0

score 10 · Accepted Answer · answered Aug 27 '18 at 09:20

10

Please, provide some code. That will be very helpful.

But, for now as the error shows:

Daemon: AAPT2 aapt2-3.2.0-alpha17-4804415-windows Daemon #0

It means you must have some error in your XML files (layout files or drawable files), check your recent history of your XML file if you are working on Android Studio

right click on xml file-> Local history-> show History

or look for any error that XML file is showing.

values.xml:352: error: resource android:attr/popupPromptView is private.

And also refer to this error in values.xml file

answered Aug 27 '18 at 09:20

Deepak Kumar

677
1
8
22

Your comment made me realize I needed to change my compile sdk to 28. Thank you. – casolorz Oct 09 '18 at 18:07
In my code i used ===============>>>> its shwoing resource linking failed. – Gyan Swaroop Awasthi Apr 13 '21 at 14:37

score 6 · Answer 2 · answered Oct 09 '18 at 16:36

6

It happened to me twice, and both times it was an xml spelling error, and the error message was not very useful. The best way to identify a problem is to Analyze -> Inspect code -> search for clues in the "Syntax error" and find the xml with an error.

answered Oct 09 '18 at 16:36

despecher

806
6
15

Very useful for ur help! – himaChen Apr 27 '21 at 10:40

score 6 · Answer 3 · edited Feb 22 '19 at 04:46

6

I get this error while creating the legacy icons (Image asset) tool - I find that the Android studio does not close <Vector> tag in ic_launcher_foreground.xml. I have to fix these errors by adding manually the close tag </vector>

edited Feb 22 '19 at 04:46

Balaji Birajdar

2,394
1
23
29

answered Feb 22 '19 at 01:45

NELSON RODRIGUEZ

309
3
6

Same problem after creating a custom launcher icon (Android Studio 3.4). This solution fixed it. – sysseon Jun 06 '19 at 09:56

score 0 · Answer 4 · answered May 18 '21 at 14:25

I made the silly mistake, I got this error after adding a new XML file in drawable. After going through my recent changes found that my tag in drawable started with .. and hence ended up with this error. Removed the .. from the start of my <xml tag and issue resolves. :D

score -1 · Answer 5 · answered Jan 28 '19 at 05:53

-1

update all dependencies from your build gradle issue resolved

answered Jan 28 '19 at 05:53

Leo Johny Thayyil

137
1
9

3

Hey, just a heads up since this is your first post. This is not an answer to the question. It's an instruction that doesn't explain the issue at all. In the future for other people that might come across this, more context is always more helpful. – charliebeckwith Jan 28 '19 at 06:14
by just upgrading my dependency issue solved. will you explain it in proper manner? – Leo Johny Thayyil Jan 30 '19 at 12:01

Android resource linking failed

5 Answers5

Linked