Infeasible
Status Update
No update yet.
Comments
na...@gmail.com
I don't think this is related to Gradle itself. This is how Android handles resources.
Adam, do you have an idea of what's going on here?
Adam, do you have an idea of what's going on here?
va...@google.com
du...@google.com
It seems the way Android handles the resources of type <item type=string> is flawed.
If gradle resValue generated the String resources using <string> tag instead of <item type=string> this would not be happening.
BTW, i don't see much advantage on using generic <item> tag in this case.
If gradle resValue generated the String resources using <string> tag instead of <item type=string> this would not be happening.
BTW, i don't see much advantage on using generic <item> tag in this case.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
What you expected to happen:
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):