getting " 'android:icon' attribute: attribute is not a string value” error while uploading an APK to the play store

Question

Background

After so many hours of my free time, I\'m ready to publish my very first app to the play store, but sadly I\'m having difficulties uploading the signed app.

Answer 1

I was getting the same issue today and the @Rahl_Pryde's solution worked fine with a minor change.

In my case, the problem was an android transparent res color to some of my Activity icons. But changing to a local transparent color doesn't fixed the problem.

It fixed when changed the icon from a transparent color to a 2x2 transparent png.

Answer 2

In my case the problem was occuring because I changed package name before releasing and forgot about changing directory names. Project was still compiling but it was impossible to release it on google play.

Check in any java file if you have red underlined package name with error

'Package name xxx.yyy.zzz does not correspond to the file path 'xxx.eee.zzz'.

Answer 3

I know that there is correct answer, but i believe that my experience can help some one...

so i receive the same error:

ERROR getting 'android:icon' attribute: attribute is not a string value

but my problem wasn't related with icon!!!

The reason why I get this error was here:

android:label="@string/app_name"

My project has 3 different languages, but the main string.xml was without @string/app_name... and this was the reason!

so be careful!

Answer 4

I think I was hit by this issue (or something similar, not sure) when I tried to use an XML drawable as the icon (to add padding, etc. to the PNG image). I don't think your issue is the same though, since you seem to refer to the PNG file directly.

Some suggestions to try (to track down the problem by process of elimination):

• Remove res/drawable-mdpi/app_icon.png file and see if you got a different error.
• Remove all android:icon attributes in your manifest and see if you still got the error.
• Rename any other resource named app_icon in the project to something else.

If all else fail, I would probably start stripping out the external JARs and library projects (and probably temporarily commenting the code that refer to them) just to see if the error was triggered by any of them. Or maybe start fresh with a bare minimum AndroidManifest.xml and add your stuff one item at a time.

Another idea is to try to figure out why aapt is producing the error. Maybe download the source and try to debug it?

Answer 5

In my case I have solved it by using always default res folders ie values, values-es, values-ca

Answer 6

If you are using any android system icons as activity icons (i.e. manifest contains <activity ... android:icon="@android:drawable/... ) , they could be the problem. If you are, try copying these icons into your project. Using them elsewhere should be no problem since badging doesn't touch those.