Error - Android resource linking failed (AAPT2 27.0.3 Daemon #0)

AndroidGradleBuild

Android Problem Overview


I have this error

I am try reinstall android studio and remove .gradle folder , any solution please?

    Error:FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:processDebugResources'.
> Android resource linking failed (AAPT2 27.0.3 Daemon #0)
  Command: C:\javasdk\build-tools\27.0.3\aapt2.exe link -I\
          C:\javasdk\platforms\android-26\android.jar\
          --manifest\
    

      
  C:\Users\Jalal D\.gradle\caches\transforms-1\files-1.1\fonticon-0.1.8.aar\2b09376fc14469ba65fc8e4d85c2eed1\res\values\values.xml:19:5-25:25: AAPT: error: resource android:attr/fontVariationSettings not found.
      
  C:\Users\Jalal D\.gradle\caches\transforms-1\files-1.1\fonticon-0.1.8.aar\2b09376fc14469ba65fc8e4d85c2eed1\res\values\values.xml:19:5-25:25: AAPT: error: resource android:attr/ttcIndex not found.
      
  error: failed linking references.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 3s

Android Solutions


Solution 1 - Android

The Android resource linking failed error can also appear if you have an error in any of your XML resources. In my case I was using the following line twice in one of my XML drawables in drawable folder:

<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>

I removed the duplicate line and the error disappeared. The error was a bit misleading:

> Android resource linking failed > Output: /Users/johndoe/Desktop/myapp/app/src/main/res/layout/activity_main.xml:2: > error: resource drawable/bg_main (aka > com.example.myproject:drawable/bg_main) not found.

According to the above error, the first thing you need to do is to proof read all the drawable resources that are accessed in the activity_main because the chances are higher that you will find the error. In the worst case scenario you might end up checking all your resource files.

Solution 2 - Android

Had exactly the same problem. Solved it by doing the following: Searching for and replacing com.android.support:support-v4:+ with com.android.support:support-v4:27.1.0 in the platform/android directory.

Also I had to add the following code to the platforms/android/app/build.gradle and platforms/android/build.gradle files:

configurations.all {
resolutionStrategy {
    force 'com.android.support:support-v4:27.1.0'
}}

Edited to answer "Where is this com.android.support:support-v4:+ setting ?" ...

The setting will probably(in this case) be in one of your plugin's .gradle file in the platform/android/ directory, for example in my case it was the starter-barcodescanner plugin so just go through all your plugins .gradle files :

enter image description here

Double check the platforms/android/build.gradle file.

Hope this helps.

Solution 3 - Android

Note: Android Studio spits out a load of crazy errors like this if you upgrade the support libraries to 28.0.0 and your compileSdkVersion is not 28 also.

Solution 4 - Android

Problem fixed for me by replacing compileSdkVersion 23 with compileSdkVersion 28 in build.gradle (Project: build).

Solution 5 - Android

In your layout (xml) files almost every element has a property i.e. "id" which, can be assigned in order to refer to it from the java/kotlin code or from the xml itself.

Now sometimes or in some versions of Android Studio errors in xml files is either not reported or some random error is thrown while compiling, of which, this thread is an example i.e. when assigning an id to an element or when refering to another element in the layout we use the ID but ids are not just written like any other word rather they are prefixed by these characters: @+id/, otherwise the above error is thrown.

Hence the solution below should be considered:-

I resolved it by adding @+id/ before all my IDs.

i.e. @+id/your_item_id

Solution 6 - Android

If you are using Windows 10, and Android Studio 3.2, you can simply go to the app's build.gradle, and change the version.

Under dependencies, change version, and build/sync

Solution 7 - Android

feel so stupid - (for whatever reason) i had one empty xml in drawable folder. and AS produced dozens of unrelated errors ><

so, my general advice would be the same - check briefly every resource file.

Solution 8 - Android

com.android.support:support-v4 just recently got update and maybe affect to plugin that use updated version in their dependencies. But if you cannot find in the dependencies (like if you use crosswalk plugin), just put this code in top of your code gradle plugin (no need to add on build.gradle).

configurations.all {
resolutionStrategy.force 'com.android.support:support-v4:24.0.0'
}

Example location to put the code in crosswalk plugin here

Feel free to edit version of com.android.support (DO NOT USE THE 28.0.0) because thats the problem

Solution 9 - Android

I imported new colors to my project and got the same problem. So I opened styles.xml and re-assigned items to colors using new colors names.

Solution 10 - Android

I had the same problem and solved it by going to File -> Project Structure... -> Suggestions and then Apply all. Like suggested by @JeffinJ I think the problem was because of the Gradle plugin update.

Solution 11 - Android

There should be some error in resource files. It mean is there may be miss typed value of attributes. Go through the resource files and correct these value and enjoy the work.

Solution 12 - Android

There can be multiple reasons for this problem and these reasons are mainly in the resource or app level build.gradle file.

In my case, a view in the resource file didn't had the required dependency included in the build.gradle file.

So, make sure to include all the required dependencies in the build.gradle file.

Solution 13 - Android

Check your Gradle plugin version. Try downgrading it if you have updated to a newer version just before this issue showed up. Go to File -> Project Structure. Change to the previous version.

Solution 14 - Android

I was missing this line at the top of one of my XMLs:

<?xml version="1.0" encoding="utf-8"?>

Solution 15 - Android

Try update latest build version, target and compile version and also update dependencies but not works for me

In my case change <meta-items/> to <meta-data/> in manifest works for me...

Hope its helpful for someone...

Solution 16 - Android

I had the same problem, but it was because in my buttons layout_width/height I forgot to put dp at the end when editing them. Added dp and problem fixed :/

Solution 17 - Android

It may sound banal, but for me Build > Clean Project fixed this error without any other changes.

Solution 18 - Android

For me, the error appeared after changing my launcher icon using Asset Studio. Turns out that the ic_launcher_foreground.xml file that was generated was missing the following line at the top of the file: <?xml version="1.0" encoding="utf-8"?>

Solution 19 - Android

Found one of the reasons which causes this problem

When we try to use any

> string,style,color,etc,

in manifest file that is not present in values (string.xml,style.xml,color.xml,etc,) then this type of error occurs

Solution 20 - Android

In my case I accidentally wrote:

app:displayViewTitle="@string/instructions_defineExtract_confirm_email"

Interestingly, Android Studio were able to navigate the string via CTRL+click. It was just giving Build Time error. Changing to standard "dot seperation" did the trick

app:displayViewTitle="@string/instructions.defineExtract.confirm.email"

Solution 21 - Android

i got the same bug, and i fixed it when i close the AndroidStudio and delete the dir like C:\Users\Jalal D\.gradle\caches\transforms-1\ in the build error info.

Solution 22 - Android

I was having similar problem but I came out of the solution the problem was that you were using any thing in the dependency that correspond to same domain but with different versions make sure those all are same

Solution 23 - Android

I was facing same issue and it is resolved by removing error from resource files like style, colors files in values folder. In my case, error in style colors as below:

 <style name="AppTheme.AppBarOverlay" parent="ThemeOverlay.AppCompat.Dark.ActionBar">
    <item name="android:textColorPrimary">**@color/colorPrimary**</item>
    <item name="android:textColorSecondary">**@color/colorPrimaryDark**</item>
</style>

Solution 24 - Android

Changing the version of the support library of the last one enabled (28.0.0) by the previous (27.1.0), the error Android Resource Linking Failed disappeared.

It should be noted that version 27.1.0 is the maximum allowed in our implementations, which works, but you could use an older one if you wish. And this has to be used in all dependencies that start with the string com.android.support:

project/app/build.gradle

implementation "com.android.support:appcompat-v7:$rootProject.supportLibraryVersion"
implementation "com.android.support:support-v4:$rootProject.supportLibraryVersion"

project/build.gradle

ext {
    supportLibraryVersion= '27.1.0'
}

Then, Sync Project with Gradle Files

GL

Solution 25 - Android

Same issue occurred for me, but before getting this error, my app was running. So I just did undo 2/3 times. And did changes again. And build app.app ran successfully.

Solution 26 - Android

I've come across the same issue after adding the following dependency:

implementation 'com.evernote:android-state:1.4.1'
annotationProcessor 'com.evernote:android-state-processor:1.4.1'

And the reason was that latest version of evernote uses dependencies to AndroidX, while I had support library version 27.1.1 in my project. So there was an option of upgrading support libraries to 28.0.0, as the other answers suggest, but that was a bit tricky for a large project with lots of custom views. So, I resolved the issue by downgrading evernote version to 1.3.1.

Solution 27 - Android

I'm using Studio 3.3.1 Build from Jan 28.

For me I was getting the "error android resource linking failed" pointing to a line in a layout file using ConstraintLayout that had been working correctly until today when the only change to my app level gradle file was to update the versions of:

android.arch.navigation:navigation-fragment
android.arch.navigation:navigation-ui

from 1.0.0-rc01 to 1.0.0-rc02.

The error message said something about not recognizing layout_constraintTop_toTopOf which of course is silly because it had been compiling quite happily for months.

I am already on 28.0.3 of build tools and compileSdkVersion of 28. I've been using androidx.appcompat everywhere for a while now (converted this project months back to androidx).

I first went through a project clean (no help), and invalidating cache/restart (no help). The layout in question had been originally defined using

<TextView>, <EditText> and <ImageView> components (which had been working fine until today).

But after reading the above answers I thought maybe somehow there was confusion being caused here so I changed the layout to use:

<androidx.appcompat.widget

versions of all the various components. No change - still got the error.

I then deleted the <androidx.appcompat.widget.AppCompatTextView block that was causing the compilation error. I changed all references to it in the other widgets to refer to "parent" instead. Did a Make. This time the compile completed without error.

So something strange in that widget definition I thought....here is what it was:

<androidx.appcompat.widget.AppCompatTextView
    android:id="@+id/contact_firstname_label"
    android:layout_width="0dp"
    android:layout_height="wrap_content"
    android:text="@string/contact_fname_label"
    android:gravity="end"
    android:textAppearance="@android:style/TextAppearance.Material.Small"
    app:layout_constraintTop_toTopOf="parent"
    app:layout_constraintLeft_toLeftOf="parent"
    app:layout_constraintRight_toLeftOf="@+id/contact_detail_fname"
    app:layout_constraintBaseline_toBaselineOf="@+id/contact_detail_fname"/>

I then pasted back the block I had Ctrl-V cut previously and changed the references back to that ID in the other components that reference it in the layout. Compile failed.

I cut the block again and pasted it to WordPad. Then reading from the WordPad paste, I actually typed it back in (i.e. I didn't copy/paste this time) - line by line, doing a make on the project after I typed in the minimal definition, and then again thereafter when I put in each new line. Each time the project compiled cleanly!

I don't know what to make of this. Perhaps some spurious invisible character was in the file originally?

Solution 28 - Android

In my case I styled by accident a property present only in buttons and added that style for a TextView.

<!-- applied to TextViews -->
<style name="rowStyle"> 
    <item name="android:padding">3dp</item>
    <item name="android:borderlessButtonStyle">false</item> <!-- this caused the error -->
    <item name="android:background">@drawable/textview_border</item>
</style>

Removing the row with android:borderlessButtonStyle fixed the problem.

Solution 29 - Android

  • Right click on the drawable folder and select "Show in Explorer".
  • Find the failing file in the opened file system, select them (or select the files in the entire drawable), then copy them to the drawable-v24 file (do not delete the drawable file and create it if there is no drawable-v24 file).
  • Then choose File -> Invalidate Caches / Restart and
  • restart Android Studio.

Solution 30 - Android

In case you run into this: in my case I had a translated string, but the string did not yet appear in the default strings.xml. Added the missing string to strings.xml and it got resolved.

Solution 31 - Android

In my case the error was pointing to the AndroidManifest.xml file. I had this line:

<meta-data
            android:name="com.google.android.actions"
            android:resource="@xml/popup_info.xml" />

Which, I'm not sure why Android Studio put that there. I didn't change my manifest file, and this never happened until I upgraded to version 3.5.3 - so AS must have done it for me. Anyway, the line should have looked like this:

<meta-data
            android:name="com.google.android.actions"
            android:resource="@layout/popup" />

Once I changed that, it was all good.

Solution 32 - Android

I encountered the same error and I was missing @+id/ in one of constrained

        app:layout_constraintEnd_toEndOf="btn_join"

It was fixed once I added @+id/ just like below :

        app:layout_constraintEnd_toEndOf="@+id/btn_join"

Solution 33 - Android

I was an issue like this with the drawable.

Spent almost 7 hours. tried everything from Google and SO. Nothing worked

then took rest reopned the file just watch the codes and suddenly it clicked to my mind that the image files I named as spalsh instead of splash!

Those 7 hours!!!! just only a small mistake and so much stress.

Somethings nothin works except a miracle like this

Solution 34 - Android

I changed the names and values inside my colors.xml,
and forgot to update themes.xml (night) with the new color names.
Replacing the old color names with the new names solved the problem.

Solution 35 - Android

This happened when I deleted/modified a file from the drawable folder that was being used by an xml file, reverting this back fixed the issue. But for some reason the Android Studio didn't show the exact location of the error.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionMahmoud D. AlghraibehView Question on Stackoverflow
Solution 1 - AndroidDarushView Answer on Stackoverflow
Solution 2 - AndroidRFourieView Answer on Stackoverflow
Solution 3 - AndroidDaniel WilsonView Answer on Stackoverflow
Solution 4 - AndroidJaime MontoyaView Answer on Stackoverflow
Solution 5 - AndroidSajid2405View Answer on Stackoverflow
Solution 6 - AndroidSyed RazaView Answer on Stackoverflow
Solution 7 - AndroidmjollneerView Answer on Stackoverflow
Solution 8 - AndroidAhmad AzamView Answer on Stackoverflow
Solution 9 - AndroidOleksandrView Answer on Stackoverflow
Solution 10 - AndroidcieView Answer on Stackoverflow
Solution 11 - AndroidRazzView Answer on Stackoverflow
Solution 12 - AndroidN. FatmaView Answer on Stackoverflow
Solution 13 - AndroidLenzmanView Answer on Stackoverflow
Solution 14 - AndroidciaranodcView Answer on Stackoverflow
Solution 15 - AndroidLokeshView Answer on Stackoverflow
Solution 16 - AndroidDontJudgeMeView Answer on Stackoverflow
Solution 17 - Androidmihai1990View Answer on Stackoverflow
Solution 18 - AndroidA DroidView Answer on Stackoverflow
Solution 19 - AndroidVishnu MagarView Answer on Stackoverflow
Solution 20 - AndroidOnat KorucuView Answer on Stackoverflow
Solution 21 - Android103styleView Answer on Stackoverflow
Solution 22 - AndroidShubham Kumar Gupta GgpsView Answer on Stackoverflow
Solution 23 - AndroidRKMView Answer on Stackoverflow
Solution 24 - AndroidBraian CoronelView Answer on Stackoverflow
Solution 25 - AndroidStubbornView Answer on Stackoverflow
Solution 26 - AndroidanroView Answer on Stackoverflow
Solution 27 - AndroidtfrysingerView Answer on Stackoverflow
Solution 28 - AndroidEmbid123View Answer on Stackoverflow
Solution 29 - AndroidGörkem KARAView Answer on Stackoverflow
Solution 30 - Androidea_View Answer on Stackoverflow
Solution 31 - AndroidWill BuffingtonView Answer on Stackoverflow
Solution 32 - AndroidNeeKView Answer on Stackoverflow
Solution 33 - AndroidMahendrasinh RanaView Answer on Stackoverflow
Solution 34 - AndroidJonathan ApplebaumView Answer on Stackoverflow
Solution 35 - AndroidRawlin CrastoView Answer on Stackoverflow