Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "AndroidFixManifests" parameter is not supported by the "XamarinDownloadArchives" #54

Closed
PrzemekZA opened this issue Jan 4, 2024 · 5 comments

Comments

@PrzemekZA
Copy link

PrzemekZA commented Jan 4, 2024

Hi,

After Install Plugin.MauiMTAdmob (1.0.4) I have got an errors:

  1. Error MSB4064 The "AndroidFixManifests" parameter is not supported by the "XamarinDownloadArchives" task loaded from assembly: Xamarin.Build.Download, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from the path: C:\Nugets\xamarin.build.download\0.11.4\buildTransitive\Xamarin.Build.Download.dll. Verify that the parameter exists on the task, the points to the correct assembly, and it is a settable public instance property. MyProjectMAUI C:\Nugets\xamarin.build.download\0.11.0\buildTransitive\Xamarin.Build.Download.targets 60
  2. Error MSB4063 The "XamarinDownloadArchives" task could not be initialized with its input parameters. MyProjectMAUI C:\Nugets\xamarin.build.download\0.11.0\buildTransitive\Xamarin.Build.Download.targets 52

.net7 and .net8

App can be Compiled, Run and Deploy on Android with this errors. iOS not tested yet.

@JhowDevBR
Copy link

up

@marcojak
Copy link
Owner

I'm currently investigating the issue to see if it's still present in the new version 1.1.0 just released and I'll fix if a fix is still required

@marcojak
Copy link
Owner

If meanwhile, you have a quick way to replicate the issue, let me know as it will help me to identify and fix the issue

@PrzemekZA
Copy link
Author

Steps:

  1. Create new MAUI project in VS
  2. Add plugin from Nuget
  3. Build or Publish

@marcojak
Copy link
Owner

Ok, the issue belongs to Xamarin.Build.Download (usually when multiple versions of the plugin are used).
I've just released version 1.1.1 of the plugin including that package by default.

It should fix the issue now.

Let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants