How do you migrate from XamarinBuildDownloadRestoreAssemblyAar to XamarinBuildDownloadAndroidAarLibrary? I am not able to build my Xamarin Android app and this warning is being given:
"XamarinBuildDownloadRestoreAssemblyAar is no longer supported. If your build is failing, revert to an older Xamarin.Build.Download version, or migrate your packages to use the new XamarinBuildDownloadAndroidAarLibrary ItemGroup. If your build is succeeding it is safe to ignore this warning."
I haven't found the documentation to do so.
Related
I'm building a new Xamarin Forms 5 app using VS 2022 17.1.1. Everything in the project appears to be up-to-date.
I've been working on this project for a while and never had this issue. All of a sudden it just appeared today. The last action I took was to install the Plugin.InAppBilling package, thought the package in question is not used by the Plugin.InAppBilling package.
The error is as follows:
All I can see is that the shared project is using System.Numerics.Vectors version 4.5.0 and it seems to be dependency of Xamarin.Essentials which is version 1.7.1 in my project.
However, the version number of System.Numerics.Vectors seems to be 2.0.5.0 in the Android and iOS projects.
I found the GitHub issue here but I'm not seeing any clear resolution to this issue. Even though it appears to be a warning, in my case, I can no longer run the app because I keep getting deployment error to the Android Emulator or actual device. It simply refuses to deploy my app to the device/emulator. So, it's really NOT a warning in my case. It's a show-stopper. I'm a bit surprised about how lightly the Xamarin Essentials folks seem to have taken this issue on GitHub.
Has anyone actually resolved this issue? If so, what's the solution?
BTW, in my case both the Android and the iOS projects are throwing this error/warning and both use System.Numberics.Vectors version 2.0.5.0 even though the shared project has version 4.5.0 installed as a dependency undre Xamarin Esssentials.
I'd appreciate some pointers on how to make this issue disappear. Thanks.
At first, you can try to update the Xamarin.Essentials package in the Android and IOS project with the nuget package manager to the version 1.7.1.
And then, if the error is still here, you can right click the reference and remove the reference of the System.Numberics.Vectors 2.0.5.0 both in your Android and IOS project. Then download the System.Numberics.Vectors 4.5.0 in the nuget package manager both too.
Dependencies using groupId com.android.support and androidx.* can not be combined but found
IdeMavenCoordinates{myGroupId='com.android.support',
myArtifactId='support-vector-drawable', myVersion='26.1.0',
myPacking='aar', myClassifier='null'}and
IdeMavenCoordinates{myGroupId='androidx.asynclayoutinflater',
myArtifactId='asynclayoutinflater', myVersion='1.0.0',
myPacking='aar', myClassifier='null'}
incompatible dependencies
There seems to be a conflict between the deprecated appcompat library and Firebase
Solved the same issue by migrating the old and deprecated appcompat support library to the new androidx. Official docs here: https://developer.android.com/jetpack/androidx/migrate
I've faced the same error for a few days and only achieve success after migrating all project to SDK 28.
Update all project dependencies
File -> Project Structure
With Android Studio 3.2 and higher, go to menu Refactor -> Migrate to
AndroidX
It's worth mentioning without Migrating to AndroidX, the Gradle has been synced successfully, but when running the project I've got this error
Manifest merger failed: Attribute application#appComponentFactory...
I am building a Xamarin Forms solution (containing an iOS library, an Android library and a .NET Standard library) in TeamCity.
I have just upgraded to Xamarin Forms 3.1.0.583944. The project builds without any problem locally, but on my TeamCity build server (Windows Server 2016), I'm consistently getting the following error:
C:\BuildAgent\work\f12265fda07473c1\src\packages\Xamarin.Forms.3.1.0.583944\build\netstandard2.0\Xamarin.Forms.targets(44,
3): error XF002: Xamarin.Forms tasks do not match targets. Please
ensure that all projects reference the same version of Xamarin.Forms,
and if the error persists, please restart the IDE.
I have tried downgrading Xamarin Forms, and rebooting the build agent. Neither of these has succeeded.
UPDATE: There is a new error:
C:\BuildAgent\temp\buildTmp.nuget\packages\xamarin.forms\3.0.0.561731\build\netstandard2.0\Xamarin.Forms.targets(44, 3): error XF002: Xamarin.Forms tasks do not match targets. Please ensure that all projects reference the same version of Xamarin.Forms, and if the error persists, please restart the IDE.
For some reason, the agent is looking for Version 3.0.0.561731. But that is no longer anywhere in the project. I had deleted the entire C:\BuildAgent\temp\buildTmp\.nuget\packages\xamarin.forms\3.0.0.561731 folder, but it has come back.
ADDENDUM: I notice that every time I upgrade Xamarin.Forms to this version via NuGet, it fails to uninstall the old package, and I have to restart Visual Studio to complete the process. This happens without fail. I am fairly sure this is connected to the breaking build, but that is more due to speculation and experience than concrete analysis.
I found out how to fix the problem, but it's not clear to me why it would manifest in the way it has -- locally and even when I RDP onto the build agent, it builds without trouble, but when I run the build agent from the TeamCity console I hit these compilation errors.
One of my dependencies is a NuGet package, which itself has a dependency on Xamarin Forms. Fortunately, I own that NuGet package, and was able to upgrade its Xamarin Forms version to the latest available package. If I didn't own that package I would be completely stuck though -- so this is only a partial solution.
The above answer was quite helpful for me . I would like to add a couple of additional notes though. I was facing this issue when I was using Xamarin Forms 3+ and my local build was being really inconsistent with the same error "Xamarin.Forms tasks do not match targets. Please ensure that all projects reference the same version of Xamarin.Forms, and if the error persists, please restart the IDE.". Then I cleared my local NuGet cache and rebuilt the project and saw that there were other NuGet package versions being pulled for Xamarin Forms when I did a NuGet restore. I then reversed the ordering of the NuGet packages starting with Xamarin Forms and it all worked fine.
I have a Cordova (v5.2) app that I run on iOS (platform v3.9.1) and Android (platform v5.0). Is it best to upgrade Cordova from the command prompt, and then manually look for plugin updates, or should I look for plugin updates first then update Cordova? Also, I have recently upgraded from XCode 7.2 to XCode 8 and it is asking me to make changes to recommend project settings, this appears to break thinks. Should I allow XCode to make changes to the project, or should I upgrade Cordova first? I'm looking for a workflow and best way to manage these updates. Any advice is appreciated, thank you.
I would upgrade your Cordova platform first. The main version that I pay attention to is the cordova platform version. So in your case cordova-ios#3.9.1 and cordova-android#5.0.0. These packages are what control the cordova lib that gets injected into your native project. They also determine which version of Xcode you can use.
The cordova-cli pins certain platform versions by default when you run cordova platform add <platform_name>. I usually stick with the most stable release of cordova-cli for my needs and then add specific platforms (usually the latest) manually. cordova platform add ios#lateset.
Any partiular reason you're cordova#5.2, cordova-ios#3.9.1 , and cordova-android#5.0.0?
Infact you can also create a new project after cordova update and add the respective platforms and plugins so that the existing working project will be intact for reference.
If you wanna follow this approach then check out this following SO post. Even that post is related to porting cordova app from one PC to other, the steps still holds good even in this case. Hope it helps.
You should upgrade Cordova first (it's better if you install it globally with npm install -g cordova ).
After that, to update all of your plugins, you just have to remove them and readd them to your project, they will automatically be updated to be compatible with the last Cordova version.
cordova platform remove android
cordova platform add android#5.X.X
If you use the above method, be aware that any changes you made to the android platform folder will be lost (editing the contents of this folder is discouraged).
Alternatively, you may attempt to use the platform update script. For non-CLI projects, run:
bin/update path/to/project
For CLI projects:
Update the cordova CLI version. See The Command-Line Interface.
Run cordova platform update android#5.0.0 in your existing projects.
I'm working with Android Studio (Beta) 0.8.14.
I wanted to update the Gradle distribution and the Gradle plugin in my project, so I started manually changing the lines:
classpath 'com.android.tools.build:gradle:0.13.+' (in build.gradle)
distributionUrl=https\://services.gradle.org/distributions/gradle-2.1-all.zip (in gradle-wrapper.properties)
by upgrading to, respectively, 1.0.0 and 2.2.1. Then I tried to use different combinations found here on SO, e.g. 0.14.4 and 2.2, as none of these seemed to work. For each combination I got (after syncing and downloading what needed) some error, like:
AssertionError: null
AssertionError: com.android.tools.idea.gradle.project.AndroidGradleProjectComponent#71c8dfe3
UnsupportedMethodException
Unsupported method: SourceProvider.getJniDirectories().
The version of Gradle you connect to does not support that method.
After some research I thought this might be related to AS itself. Looking for updates in different channels brings me either to AS 0.9.9
This patch will allow you to update from 0.x to 1.x. After updating,
please check for updates again to install 1.x.
or to AS 1.0.2.
When trying to update, I get hundreds of errors related to Android Studio not deleting some files in android_SDK_folder/sources/android-21 , mainly.
This issue has some references here on SO. Known fixes are killing java processes during the update, which was unsuccessful for me, and launching Android Studio as admin, which doesn't look like a great idea to me (and I wouldn't know how to on OS X).
I'm stuck. My questions are:
are the Gradle syncing errors due to my old build of Android Studio?
if so, what can I do to update? I don't think I should uninstall and then get 1.0.2, as the message I reported says I can patch to 0.9.9 and then to 1.x. Is this the only thing to do?
Yes, your Gradle syncing errors are due to a mismatch between the plugin and the version of Android Studio. If you want to use v1.0.0 of the plugin, you need to be running Android Studio 1.0 or later.
As for upgrading, my advice would be to do a clean reinstall of 1.0; it will be easier than trying to spend a lot of time figuring out why the upgrade isn't working. I forget where the SDK is installed in 0.8.14, but we're encouraging/requiring users to have the SDK located outside the application directory itself, so it should help avoid future SDK woes with upgrading/reinstalling Android Studio itself.
If the SDK is currently installed inside Android Studio's directory and you don't want to re-download it, you could move it out to a more sensible place before reinstalling, and point the new installation at it.