Luckily I hadn’t had the chance to update that yet. When I switched to the system wide copy it suddenly started working. You switch between directories using the following panel under visual studio: What that implies is that you have two copies of the same thing on your machine ( as a matter of fact Xamarin asks you which one you want to use when you first install it). Īt the beginning it didn’t make any sense so I tried switching between the directory that Xamarin points to for the Android SDK ( C:\Users\\AppData\Local\Xamarin\MonoForAndroid\AndroidSDK) and the system wide system copy of Android SDK which could be found at C:\Program Files (x86)\Android\android-sdk. It can also compile resources into binary assets. This tool is part of the SDK (and build system) and allows you to view, create, and update Zip-compatible archives (zip, jar, apk). Note: aapt stands for Android Asset Packaging Tool.
After that I started facing the following errors: It all started with updating to Android SDK Build-tools version 24 manually using the SDK manager shown above. What is more important is not the resolution but rather the journey that I embarked on to resolve the issue. The short story (after debugging every stage of the tool chain with a colleague of mine) is that Xamarin.Android is not yet fully compatible with this version. Of course, being a good citizen meant that I used the Android SDK Manager to update to the latest version.
Google recently released a new final version “24” of the Android SDK Build-tools package. Senior Developer consultant, Wael Kdouh, walks us through what it takes to get Xamarin.Android working with the latest “24” SDK Build-tools package.
0 kommentar(er)
