I\'m fighting with that issue for 2 days already and can\'t find any solution.
I have an Xamarin Android app in Visual Studio 2017 consisting of three projects:
I had the same issue when I added a new image as a resource.
There was a '-
' in the file name (Invalid resource name character). I renamed & removed that character and all good.
Resource name can only consist of 0-9,a-z or A-Z or combination of any.
Simply it worked.
Check to see if there are any unused entries in resources.designer.cs if there are any manually remove those entries. This will fix the issue.
Another reason for this error, if that the android NDK (not android SDK) isn't right, change de version can resolve the problem: go to Tools/Options/Xamarin/android Configurator and change de folder, in my case I've three, the last one can't compile, but the second folder with version xx.r11c
do it.
I've finally found what was the issue. It wasn't related to any component from SDK Manager or VS version.
Following localization tutorial from developer.xamarin.com, I played a bit with Strings.xml
in my Android project. I wanted to have my Activities Label taken from resources as well, so in the ActivityAttribute
I defined:
[Activity(Label = "@string/peopleListTitle")]
and added this value in Strings.xml
file:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!-------Other resources values ----->
<string name="peopleListTitle">People List</string>
</resources>
In that case my build is failing with above-mentioned error:
The file "obj\Debug\android\bin\packaged_resources" does not exist
When I change ActivityAttribute
to use a string directly:
[Activity(Label = "People List")]
the build is passing without any issues.
I managed to find a solution, but actually I don't know why it's not building when I try to use Label text defined in Strings.xml
.
BTW, I managed to find what's the problem by setting build output verbosity to Diagnostic
in Tools -> Options -> Projects and Solutions -> Build and Run which gives a detailed info why the build failed in the Output window.
Had the same error, the way I got over it was crank up the Android SDK manager and install all updates and remove any obsolete packages. This happened to me because I was targeting something newer which was not installed.