Ошибка android resource linking failed

[SOLVED] Android resource linking failed Error: failed linking file resources.

• Posted by Finco Agbontaen
• 2 Comments
• Categories: Android Errors & Solutions, Tutorials

This error sometimes also comes as “Android resource linking failed” is another frequent and vague error in Android Studio. The solution sometimes could be quite boring and painful but I assure you, this error is absolutely nothing serious.

Cause

The error shows up when Gradle encounters an error (Usually a syntax or typo error) in one or more of your XML files.

Most of the XML files are located in the res folder, however, you might still find some outside the res folder. For example, the AndroidManifest.xml located in “/src/main/AndroidManifest.xml”. Here is an example of a layout file that would give the “Error: failed linking file resources” error.

Note the “android:endCollor” attribute.

Solution

The solution to the error is obvious, right? All you have to do is go through each of your XML files to figure out where the error might be. This could sometimes be time-consuming but be rest assured that the error will disappear as soon as you find and fix the problem child (problem XML).

You might be lucky and Android Studio will point you in the exact direction as shown in the screenshot below:

Other times like when you are using an older version of Android Studio, the error would not be this specific.

Tips to finding the problem XML quickly

If you have a lot of XML files and it would be just too difficult to go through them one after the other, you could use the following tips to make the process easier:

1. Undo: Most times, you are already halfway through a project before you experience this issue. Meaning that it was a recent change to one of your XML files that caused the issue. If that is the case, you can try to undo your recent change to the XML files. To undo, simply use the key combination: Ctrl+Z.
2. Open every XML file: The second method involves simply opening every single XML file in your project (Without scanning). The reason for this is that sometimes, after opening the problem XML file, Android Studio then detects the error and underlines it.

If you enjoyed this post, feel free to share it. If you have any questions, feel free to ask them in the comment box below. 🙂

Источник

How to Fix Android Resource Linking Failed Error

“Android Resource Linking Failed” is one of the commonest error messages encountered by Android developers while working with Android Studio. Most of them usually cannot figure out the exact cause of the issue and fix it. It’s obviously a boring and painful job to debug the whole code and get rid of the resource linking problem. But today we’ve come up with a sure-shot solution for the problem and we’re damn sure that you can fix it today itself by spending a couple of minutes.

Although it not a serious issue, it’s a good thing to know how the issue arises and what might be the reasons behind that. So let’s explain things clearly so that you can eliminate such errors in the future.

Error: failed linking file resources – The Cause

Usually, this error occurs while the Android Studio Gradle encounters some errors in one or more of your XML files. This may be sometimes a syntax error or simple a typo.

Although the XML files are located in the res folder, you need to check whether there are any files located outside of the folder and you have to debug that too. I’ll explain with an example:

Suppose the AndroidManifest.xml is located in “/src/main/AndroidManifest.xml”.

A layout file that probably gives the Android resource linking failed error looks something like this:

Not down the android:endCollor attribute .

Android Resource Linking Failed Error – The solution

For fixing this error, all you need to do is to manually check each of the XML files and find out the issue. Just run the code and the Android Studio will help you figure out the issue most of the time. This is because the latest version of Android Studio will point of the error specifically so that you can save the time to debug it.

Just in case, you are using an older version of the Android Studio, the error would not be specific and will take some time to debug.

Moreover, if you have a few numbers of XML files having issues, it will be a tiresome task to get rid of the error. So in order to tackle this situation, we have some methods to quickly find out the file and rectify the issue.

1. Open Every XML file

One of the methods is manually opening every XML file without scanning or running. This is helpful because when you open a file Android Studio will detect the errors if any and underline the codes where the issue has crept in. This way you can quickly identify where is the problem and resolve it without having many headaches.

2. Run a Stacktrace

It’s obvious that if you have a big project, it will be a nightmare to check each and every XML file. So one of the best workarounds for this error is to open the Android Studio Terminal and run a Stacktrace. This will show you which file is causing the issue. To do a stacktrace run the following command in the Android Studio terminal.

gradlew build —stacktrace

3. Undo the Changes

This is another hack by which you can get rid of the Android resource linking failed error. Undoing the last changes may sometimes help you quickly. In most times this issue will arise when you are halfway through a development project. This means that one of the recent changes is responsible for generating such an error. So just reverting the last commits can definitely help you out to tackle this situation.

For this to do, press CTRL + Z to go a revert a single change. Likewise, debug the code after each undo and you will quickly find out where is the error. Once you find it out, you can correct it with ease as it’s not kind of a big deal.

Conclusion

Hopefully, by now, you have learned a few workarounds to troubleshoot the android resource linking failed issue and get rid of that with ease.

If you find this article useful, feel free to share it and spread the knowledge.

Источник

Android resource linking failed for magicretry_fragment.xml #3

Comments

mvij commented Aug 21, 2019

When i try to build this lib using Android Studio 3.5.0, i get the following error
AGPBI: <"kind":"error","text":"Android resource linking failed","sources":[<"file":"/home/vijith/.gradle/caches/transforms-2/files-2.1/0c1b042f08a50764c3d60743091442f0/jetified-magicretry-1.0.7/res/layout-v11/magicretry_fragment.xml","position":<"startLine":120>>],»original»:»/home/vijith/.gradle/caches/transforms-2/files-2.1/0c1b042f08a50764c3d60743091442f0/jetified-magicretry-1.0.7/res/layout-v11/magicretry_fragment.xml:121: AAPT: error: resource android:attr/android:progressBarStyleSmall not found.\n «,»tool»:»AAPT»>

The text was updated successfully, but these errors were encountered:

here4learning commented Aug 22, 2019

mvij commented Aug 22, 2019

The layout file magicretry_fragment.xml in layout-v11 res folder has ?android:attr/android:progressBarStyleSmall at line 126. It should be ?android:attr/progressBarStyleSmall or ?attr:progressBarStyleSmall

here4learning commented Aug 22, 2019

yes.Correct. But it is not accessible to change the xml. . So it has to be done at Payu side.

Ranjithsp6 commented Aug 27, 2019

yes.Correct. But it is not accessible to change the xml. . So it has to be done at Payu side.

have you found the temporary solution?

here4learning commented Aug 27, 2019

Create a folder within main res folder and create the xml file according to last comment of the link »
https://stackoverflow.com/questions/57588753/aapt-error-resource-androidattr-androidprogressbarstylesmall-not-found» . it will override payumoney xml file.

Ranjithsp6 commented Aug 27, 2019

Create a folder within main res folder and create the xml file according to last comment of the link »
https://stackoverflow.com/questions/57588753/aapt-error-resource-androidattr-androidprogressbarstylesmall-not-found» . it will override payumoney xml file.

Thank you its working

himgupta229 commented Sep 4, 2019 •

What is the gradle plugin version you are using?

jakal23 commented Feb 1, 2020

Have the same problem migrating androidx

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник