Fixed: Could not find android.jar for API Level 21

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited November 2014 in Xamarin.Android

Update November 20, Xamarin.Android 4.20 promoted to the stable channel

Support for Android 5.0 API Level 21 has just been promoted to the stable channel:

  • Windows: Xamarin 3.8.150
  • Mac: Xamarin.Android 4.20.0.28
  • Xamarin Studio: Xamarin Studio 5.5.4 (build 15)

Update November 11, fixed in Xamarin.Android 4.20 on the beta channel

Support for Android 5.0 API Level 21 has just been published to the beta channel:

  • Windows: Xamarin 3.8.134
  • Mac: Xamarin.Android 4.20.0.24
  • Xamarin Studio: Xamarin Studio 5.5.4 (build 13)

Note that as with other builds on the beta channel, these builds have not yet completed the full suite of QA testing. These new versions will be promoted to the stable channel pending further QA testing and barring reports of any new problems from beta users.

Also keep in mind the following "Known Issue" from the release notes:

If your Android project was targeting the Android L Preview, you'll need to update your Android XML manifest to change version information from L to 21. Additionally, you should retarget your project's framework to use version 5.0 or, alternatively, set it to use the latest available framework version

Update October 30, not yet fixed in Xamarin.Android 4.18.1

This is just a quick update to confirm that the fix for this issue with the Android 5.0 API Level 21release is not yet fixed in the recently released hotfix (Xamarin.Android 4.18.1 on Mac, Xamarin 3.7.248 on Windows).

The hotfix addresses a number of other slightly older issues (see below for a few more details). The fix for the Android 5.0 API Level 21 release has been committed to the development branch, and will be included in the next Xamarin.Android stable release.


October 20

The Xamarin.Android version currently available supports API Level 21 "L" preview, but it does not yet support the final Android 5.0 API level 21 release. Updated support for Android 5.0 API level 21 is currently a top priority for the Xamarin Android team. They are working to get a compatible build out as soon as possible.

While the Android team is still working on the final Android 5.0 API level 21 release, you will see one of the following errors when you first install Android 5.0 API level 21.

In Visual Studio

Error 1 Could not find android.jar for API Level 21. This means the Android SDK platform for API Level 21 is not installed. Either install it in the Android SDK Manager (Tools > Open Android SDK Manager...), or change your Xamarin.Android project to target an API version that is installed.

On Mac

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Could not find android.jar for API Level 21. This means the Android SDK platform for API Level 21 is not installed. Either install it in the Android SDK Manager (Tools > Open Android SDK Manager...), or change your Xamarin.Android project to target an API version that is installed.

Workarounds

  1. Change your project so that it targets API 19 or lower.

  2. Rename your android-21 folder to android-L.

    Windows (assuming the default android SDK install location in %LOCALAPPDATA%)
    From: %LOCALAPPDATA%\Android\android-sdk\platforms\android-21
    To: %LOCALAPPDATA%\Android\android-sdk\platforms\android-L

    Mac (assuming the default android SDK install location in ~/Library/Developer/Xamarin/)
    From: ~/Library/Developer/Xamarin/android-sdk-macosx/android-21
    To: ~/Library/Developer/Xamarin/android-sdk-macosx/android-L

    Note: This should only be used as a temporary fix, and there's a chance it will cause other problems. Essentially this method "pretends" that the android- 21 release has the same API as the android-L release.

  3. Temporarily downgrade back to the Android API Level 21 "L" preview:

    Windows
    a. Delete the %LOCALAPPDATA%\Android\android-sdk\platforms\android-21 directory (or move it to a backup location)
    b. Extract https://dl-ssl.google.com/android/repository/android-L_r04.zip into %LOCALAPPDATA%\Android\android-sdk\platforms to create an "android-L" folder.

    Mac
    a. Delete the ~/Library/Developer/Xamarin/android-sdk-macosx/android-21 directory (or move it to a backup location)
    b. Extract https://dl-ssl.google.com/android/repository/android-L_r04.zip into ~/Library/Developer/Xamarin/android-sdk-macosx to create an "android-L" folder.

    If you like, you can probably skip step (a), and leave both folders installed side-by-side.

Posts

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
  • JeremyKolbJeremyKolb USMember ✭✭✭
    edited October 2014

    Change your project so that it targets API 19 or lower.

    This doesn't actually work at least in Visual Studio. You will still get the error for binding projects.

  • KHTehKHTeh USMember
    edited October 2014

    Hi,
    I tried option (3). However, the device emulator for this API 21 failed to start. I am sure that I have had Intel Atom x86 an x86_64 system images installed.

  • MalcolmSwanMalcolmSwan USMember

    No android-21 installed
    No android-20 L preview installed
    After auto-update to Xamarin Studio 5.5.2 no Xamarin.Android according to Xamarin Studio
    No option to open the visual designer (no content or source button in Main.axml)
    No "General" item Project Options > Build anymore
    Uninstalling Xamarin - Not sure if I'll bother reinstalling considering that there was an issue after the last auto-update
    Thank You!

  • WilliamAndrewSowerbyWilliamAndrewSowerby GBMember ✭✭
    edited October 2014

    Workaround 1 worked but I now get the following error when building in Release mode:

    Error 56 You need to add a reference to Mono.Android.Export.dll when you use ExportAttribute or ExportFieldAttribute. C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets 1087 3 AppName

    The error is removed when I add Mono.Android.Export.dll to the References. Why do I now need this assembly which was never required before? Using Visual Studio 2010 and:

    Xamarin 3.7.230.0 (e78d10d6993f95fc3ebe791aeb4aacff165bf8bb)
    Xamarin.Android 4.18.0.39 (0ef616ae42005ece52f6df7aa1e093ceb11998f8)

    and does it matter?

  • Crave_ErikCrave_Erik NLMember

    Any update on when we can expect support for the official API 21?

  • PulsarPulsar USMember

    I tried to do the third option and the error finishes. However I have now problems with all the using Android.(whatever). the error said:
    Error CS0234: The type or namespace name App' does not exist in the namespaceAndroid'. Are you missing an assembly reference? (CS0234) (RecyclerViewSample)

    Any idea??

  • mobiRicmobiRic USMember

    I think it is a pity that the Xamarin team tries to point the finger at Google's auto-update. I have a fresh install done yesterday with no auto-update - the fresh install gave me the (released) Android 21 SDK, and Xamarin is looking in the wrong folder android-l instead of android-21.

    Thanks to scriptam for explaining how to downgrade the Xamarin Droid project to use API 19. That is a great help to me, as a totally new user.

  • JeremyKolbJeremyKolb USMember ✭✭✭

    Agreed. You would think that Xamarin would have released an update to fix this build issue. I think they're more interested in iOS than Android.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited October 2014

    The fix has been committed to the development builds and is on the way to the stable channel. Unfortunately the Xamarin.Android release process has become quite complicated recently due to several other bugs:

    These 4 problems are being addressed in a Xamarin.Android 4.18.1 hotfix release that's currently undergoing final approval for release. Again unfortunately, it was not possible to get the more recent Android API 21 fix into this release because that would have delayed the fixes for these other older issues.

    @mobiRic‌

    I think it is a pity that the Xamarin team tries to point the finger at Google's auto-update. I have a fresh install done yesterday with no auto-update - the fresh install gave me the (released) Android 21 SDK, and Xamarin is looking in the wrong folder android-l instead of android-21.

    If the Xamarin combined automatic installer is currently installing the Android 21 SDK, then that is a separate bug that I was unaware of. I just ran the combined automatic installer from http://xamarin.com/download on a clean Windows system. It did not install Android 21 SDK in my case. Did you download a recent version of the automated installer when performing the clean update? Or is the issue you're seeing that you already had Android 21 SDK installed before running the combined Xamarin installer, so you're just using the combined installer to install Xamarin and not the Android SDKs? In that case, you are correct: you will need to use one of the workarounds because the fix for Xamarin.Android has not yet been released.


    Just in case it might be helpful to know, the Android team is independent of the iOS team (and has approximately the same number of developers), so delays on Android are unrelated to any work that's happening on iOS.

  • mobiRicmobiRic USMember

    Brendan thanks for the reply.

    I have been an Android developer for many years, and based on my experience, I chose not to install the "L" Preview SDK on my production machine for fear that it might break something that I need for my work.

    Then when I installed Xamarin (downloaded 2 days ago, for the first time), the installer did not find my usual Android SDK installation (which I am glad about), and chose to install its own Android SDK (which is the only one I have been making Xamarin-related changes to).

    I believe it was the T-shirt Store sample app that prompted me to download SDK 21 (I am not 100% sure). I think I saw a compile error that requested SDK 21, so I used the Android SDK Manager to install it. However at this time, the actual version had been released, and it was no longer in "preview" state.

    The build errors persisted, and at closer inspection I saw that the error looks for a folder named "android-l", which is what the "preview" SDK 21 was named. However the final release goes into the "android-21" folder. So despite having SDK 21 on my machine in the correct place, Xamarin Studio was unable to find it.

    One of the related threads on this site has a comment from a Xamarin developer where he blames Google for creating this bug. As you can see from the above, that is not the case. I hope this explanation helps you guys with sorting things out.

  • JeremyKolbJeremyKolb USMember ✭✭✭

    @BrendanZagaeski thanks for the detailed response. It's important to keep the lines of communication open like this.

  • KevinFordKevinFord USUniversity, Certified XTC Partners ✭✭✭

    @BrendanZagaeski,
    Thanks for the info. This just saved my bacon.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    Hi all

    I work with Xamarin.Forms under VS2013 and - unfortunately - have installed the latest Xamarin-updates to Android.
    After update, I have various error-messages like:

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded\.\res\values-v14\values.xml 10

    To set target to API-19 on my android-project-settings (workaround 1. above) does not change anything..

    If I rename my android-21 folder to android-L (workaround 3. above) and then set the API-Level to "use latest" (or manually in the manifest-file to 21), I have the error-message:

    Attribute “theme” has already been defined
    (so I have rechanged the folder-name to android-21)

    I have lost now a full day and am not able to compile the android-project in my .forms-app.

    @BrendanZagaeski‌:

    What can I do...?

    Thanks for any answer

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    Update to my last post:
    Also workaround 3 (Temporarily downgrade back to the Android API Level 21 "L" preview) don't work :-(
    My Android-project (in my .forms-app) is dead now...
    I have lost now a full day...
    It would be nice, if I would receive some help from Xamarin (I am a paying customer)...

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @FredyWenger‌, please email Xamarin support via [email protected] (or even better, use one of the email addresses listed on https://store.xamarin.com/account/) for one-on-one troubleshooting help.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭
    edited November 2014

    @BrendanZagaeski‌:
    I have bad experience with support-mail (tried out three times in the past -> no useful response within days).
    I also don't want to pay for additional one-to-one-support because I have installed a Xamarin-Update (I have paid the XF-Licenses).
    I think, you are the specialist here...?
    You can't help me...?
    When do you expect an update, that fix the problem?

    Update: I have sent an mail at [email protected] now...

  • I clicked on the project in the Solution Pad - Project Options > Build > General but it does not list any options. Am I looking in the wrong place to change the Target Framework?

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited November 2014

    Support for Android 5.0 API Level 21 has just been published to the beta channel:

    • Windows: Xamarin 3.8.134
    • Mac: Xamarin.Android 4.20.0.24
    • Xamarin Studio: Xamarin Studio 5.5.4 (build 13)

    Note that as with other builds on the beta channel, these builds have not yet completed the full suite of QA testing. These new versions will be promoted to the stable channel pending further QA testing and barring reports of any new problems from beta users.

    Also keep in mind the following "Known Issue" from the release notes:

    If your Android project was targeting the Android L Preview, you'll need to update your Android XML manifest to change version information from L to 21. Additionally, you should retarget your project's framework to use version 5.0 or, alternatively, set it to use the latest available framework version

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:
    You wrote "Support for Android 5.0 API Level 21 has just been published to the beta channel:"

    • Windows: Xamarin 3.8.134

    Do you mean the nuget-update to XF V. 1.3.0.6275-pre1 (which is available in VS since today) with 3.8.134?
    If yes, this also should solve my problem?
    If no, where can in download the 3.8.134?
    Thanks for a quick answer.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    No need to worry about your Xamarin.Forms version. Xamarin 3.8.134 for Windows is the combined package that includes Xamarin.iOS, Xamarin.Android, and the Visual Studio extensions for Windows. You can get the beta version of that package by switching your updates channel in Visual Studio or Xamarin Studio. See: http://developer.xamarin.com/recipes/cross-platform/ide/change_updates_channel/.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:

    Now I was able to install the update.
    B.t.w.: VS2013 play's "Ping-Pong" after the update.
    Every time, I start VS2013, a message is displayed, that an new version is available. If I install it, a downgrade is installed (I have done a upgrade - downgrade - and once again an upgrade in the meantime).
    The "old" error-messages are gone now, but therefore I have a new one :-(
    See below...
    I think, I had the version-conflict's before (b.t.w.: no one can say me how to solve it).
    However, I think, the reason is:
    1>C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(794,2): error MSB6006: "aapt.exe" wurde mit dem Code -1073741819 beendet.
    As I know from the past, aapt.exe-errors are mainly related to problems with resource-files in the Android-project.
    But... I don't have changed anything since the problems have started...
    Advise please...

    ------ Neues Erstellen gestartet: Projekt: MatrixGuide.Android, Konfiguration: Debug Any CPU ------

    1> Führen Sie ggf. mit app.config eine erneute Zuordnung der System.Net.Primitives, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a-Assembly von Version 3.9.0.0 [] zu 4.0.0.0 [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Net.Primitives.dll] durch, um den Konflikt zu lösen und Warnmeldungen zu vermeiden.
    1> Führen Sie ggf. mit app.config eine erneute Zuordnung der System.Net.Http, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a-Assembly von Version 1.5.0.0 [] zu 4.0.0.0 [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\System.Net.Http.dll] durch, um den Konflikt zu lösen und Warnmeldungen zu vermeiden.
    1> Führen Sie ggf. mit app.config eine erneute Zuordnung der System.Threading.Tasks, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a-Assembly von Version 1.5.11.0 [] zu 4.0.0.0 [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Threading.Tasks.dll] durch, um den Konflikt zu lösen und Warnmeldungen zu vermeiden.
    1>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1696,5): warning MSB3247: Es wurden Konflikte zwischen verschiedenen Versionen derselben abhängigen Assembly gefunden. Doppelklicken Sie in Visual Studio auf diese Warnung (oder wählen Sie sie aus, und drücken Sie die EINGABETASTE), um die Konflikte zu beheben; fügen Sie andernfalls die folgenden BindingRedirect-Einträge zum "Runtime"-Knoten in Ihrer Anwendungskonfigurationsdatei hinzu:
    1> AcwMapFile Not There....: M:\SW\VS_2013\Xamarin\MatrixGuide\MatrixGuide.Android\obj\Debug\acw-map.txt
    1>C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(794,2): error MSB6006: "aapt.exe" wurde mit dem Code -1073741819 beendet.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:
    I have searched now the Internet for further about 4 hours...
    I have found a posting, that says, that there is a bug in Android SDK V. 21.0.1, that causes the problem.
    Link: stackoverflow.com/questions/10699439/aapt-failing-with-error-code-1073741819
    And... 21.0.1 is exactly the version, that is used in my installation although I have installed various newer versions (including 21.0.2 where the bug should be solved).
    I then have searched, where to say the android-project, which version of the SDK should be used (including low-level-search for "21.0.1" over the Android-project)... and found... nothing:-(

    Is the SDK-version hardcoded or where can I change it from 21.0.1 to 21.0.2?
    Advise please...

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:
    May I have an answer please - I'm not able to work since three days now!

    I have send my app to support - it seems as support is not able to help me.
    It seems as there is an version mismatch between Xamarin-Update and Android-sdk's...
    The only suggestion from support was, to deinstall sdk-version 21.0.1.

    If I do this:

    I have 9 error-messages:

    Attribute "theme" has already been defined M:\SW\VS_2013\Xamarin\packages\Xamarin.GooglePlayServices.19.0.0.1\lib\MonoAndroid23\19\content\google-play-services\libproject\google-play-services_lib\res\values\wallet_attrs.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'.C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v11\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v14\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v11\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v14\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v11\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v14\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v11\values.xml

    No resource found that matches the given name: attr 'android:actionModeShareDrawable'. C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\values-v14\values.xml

    10 Warnings like:
    iCCP: Not recognizing known sRGB profile that has been edited C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\drawable-mdpi\abc_ab_share_pack_holo_dark.9.png MatrixGuide.Android

    iCCP: Not recognizing known sRGB profile that has been edited C:\Users\wengerf\AppData\Local\Xamarin\Android.Support.v7.AppCompat\21.0.0-appcompat-v7\embedded.\res\drawable-hdpi\abc_ab_share_pack_holo_dark.9.png

    101 Messages like:
    Die Schemainformationen für das Attribut 'format' konnten nicht gefunden werden. M:\SW\VS_2013\Xamarin\packages\Xamarin.GooglePlayServices.19.0.0.1\lib\MonoAndroid23\19\content\google-play-services\libproject\google-play-services_lib\res\values\wallet_attrs.xml

  • JeremyKolbJeremyKolb USMember ✭✭✭

    @FredyWenger set your target SDK to 21 in the project properties.

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
    edited November 2014

    @FredyWenger‌, unfortunately I'm really just 1 more member of the support team. I don't have any more advanced knowledge about Android than the rest of the support team, and I have only a limited amount of time each week to step away from email support cases to work on forum threads.

    At first glance, at least some of the errors from this latest issue ("No resource found that matches the given name:") sound like a problem with setting the "Compile using Android version" and "Target Android version" (under "Project Properties -> Application [tab]") to versions that are too low, as Jeremy suggested. See also for example the top hit from Google. That's a fairly common problem with Android projects. I think a web search for the error should turn up some other helpful results. There might be some previous threads on the Xamarin forums about it too. If not, I'd recommend continuing the conversation via email with the support team. If you like, you're also welcome to post a new separate forum thread about it. That will help give it better visibility for other members of the Xamarin forums community to help. I suspect the underlying cause of the problem has shifted now and is no longer directly related to the primary topic of this thread ("Could not find android.jar for API Level 21"), and so a new forum thread would be appropriate.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:
    I allready have postet in two other threads:

    forums.xamarin.com/discussion/27674/project-don-t-compile-anymore-after-install-latest-xamarin-updates-to-android#latest
    and
    forums.xamarin.com/discussion/comment/88062/#Comment_88062
    Without any answer!

    As I wrote, I have tried all three workarounds described here in this thread, searched the internet for information's (for hours) and tried out all target options in the project.
    Nothing works!
    After I have installed "your" XF-integration-update, I now have the (single) "aapt.exe-error" (Code -1073741819).
    I would de-install the nugget-packages ("rollback"):
    Xamarin Support Library v4
    Xamarin.Android.Support.v4 - Version 21.0.0.0-beta1
    Xamarin Support Library v7 AppCompat
    Xamarin.Android.Support.v7 - Version 21.0.0.0-beta1
    Xamarin Support Library v7 AppCompat
    Xamarin.Android.Support.v7 - Version 21.0.0.0-beta1
    If I could... (but I can't)
    I have sent my whole project to support - without success...

    So I hope, you don't let me stay in the rain and ... ask somebody from the android-team that knows the solution, if you don't know it.

    Final note: I am a paying customer...

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @FredyWenger‌

    ask somebody from the android-team that knows the solution

    That is indeed a good next step. Since you have business licenses (or higher), that's what the support team can help you with via email. Thanks!

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @JeremyKolb‌:
    Thanks for your suggestion
    Unfortunately this don't solve the problem (still error-message "aapt.exe" ended with Code -1073741819).

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:
    Did you read my posting....?
    I have already sent my project and various mails to Xamarin-support...
    Or have I misunderstand you...?

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @FredyWenger‌, yes. I meant that you can continue to follow-up with the support team via your existing email cases because I can't offer much detailed troubleshooting help directly on the forums.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @BrendanZagaeski‌:
    As I wrote, I don't had success with the support as it seems, that the supporter also isn't a XF-Android-specialist.
    I meant, that you can establish a connection ...?

    I do not even know if it would solve the problems, if I would set up my whole machine from image of last week (and thus losing work of days), because my project is located on a network-share..?

  • DynogicDynogic CAMember ✭✭

    I had the http://stackoverflow.com/questions/10699439/aapt-failing-with-error-code-1073741819 issue as well on Xamarin.Android 4.20.

    The fix was trivial...
    Copy the contents of 21.0.2 to 21.0.1 folder in the Android SDK build tools folder. If that doesn't work, open SDK Manager and uninstall all the 21.x.x build tools. One of my Windows rigs is running the former 'patch', while my other is running the latter 'patch'... both working just fine.

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    @Dynogic‌:
    Thanks for your suggestions.
    Unfortunately, it don't solve the problem.
    After copy 21.0.2 to 21.0.1, the aapt.exe-error has gone, but therefore, I now have the error-message:
    Attribute "theme" has already been defined
    Unfortunately, also de-installation of all 21.x.x build-tools don't help (theme-error-message don't go away)...

  • FredyWengerFredyWenger CHInsider ✭✭✭✭✭

    I now was able to correct the installation. Therefore, I had to do the following steps:

    • De-install all Andorid SDK Build-Tools higher the 19.1 (only 19.1 is installed after that)
    • De-install Xamarin.Forms.Maps from nuget
      => This also de-installs Xamarin.Forms

    • Re-Install Xamarin.Forms.Maps Pre-1
      => This also installs Xamarin.Forms Pre-1

    After that, I was able to compile my project once again (after losing a full week!).
    And.. I now have the newest Pre1-Version of XF installed (I did not want that, but now have to be glad that the compile working again).
    My Project now includes the latest Xamarin.Forms and Xamarin.Forms.Maps packages (1.3.0.6275-pre1) and compile using Android SDK Build.Tools 19.1.
    It seems, as (one of the) the main problem(s) is caused from Xamarin Google Play Services Binding (19.0.0.1). That is investigated now from Xamarin (they hope, that they can push a new Version soon).
    Hope this helps someone…

  • AlbertoEstrellaAlbertoEstrella DOMember ✭✭

    Unfortunately it doesn't work for me @FredyWenger‌ (note that I'm not using Xamarin Forms).

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    @AlbertoEstrella‌

  • WilliamSRodzWilliamSRodz BRInsider, University, Developer Group Leader ✭✭

    Hi guys, I had the same problem, but I could overcome it by changing the [Project Options] (see attached file).

    Hope this helps

  • BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai

    I am now closing this thread because support for Android 5.0 API Level 21 has been included in the past 2 stable releases. If anyone hits any of the problems mentioned in this thread in the future and cannot find a fix based on the existing information in this thread, please create a new forum thread, contact Xamarin support, or file a bug report. Thanks!

This discussion has been closed.