It seems to be related to the 0.10.0 android gradle plugin. If I change it 
to com.android.tools.build:gradle:0.9.2, the problem goes away.

On Monday, May 5, 2014 4:36:08 PM UTC-7, Christopher Pickslay wrote:
>
> A build tools dependency seems to have changed today that's causing AAPT 
> to incorrectly parse one of our strings files. Doing a clean build:
>
> gradlew clean assembleDebug
>
>
> I get this error in the processDebugResources task:
>
> build/res/all/debug/values/values.xml:980: error: Error parsing XML: not 
> well-formed (invalid token)
>
>
> This is line 980 of values.xml:
>
> <string name="box_score">Box Score �</string>
>
>
> That funky character is ». It's encoded as &#187; in strings.xml, but the 
> error occurs whether the actual character or the entity appears in the 
> file. This line has not changed in over a year, but the build suddenly 
> started failing today. The same character exists in other localized strings 
> files, and the generated values.xml for those localizations are fine. If I 
> move this exact strings file to the values-en-pUS directory, it parses fine:
>
> <string name="box_score">Box Score »</string>
>
>  
> But the build still fails, as there are offending characters in 
> dependencies like Facebook and ActionBarSherlock. The build was working 
> fine with the same code today on some workstations, but running gradle with 
> --refresh-dependencies causes it to start occurring. 
>
> Is anyone else seeing this? I'm not sure where to go from here to 
> troubleshoot. 
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to