The "Xamarin.Messaging.Tasks.CreateArchiveDirectory" task could not be loaded RRS feed

  • Question

  • User158028 posted

    After the last Xamarin update with iOS 10, all of my App Store builds with True are failing with the following error.

    Severity Code Description Project File Line Suppression State Error The "Xamarin.Messaging.Tasks.CreateArchiveDirectory" task could not be loaded from the assembly C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.Messaging.Tasks.dll. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

    It's been over a week. I've done everything I can and i still can't see any threads discussing this. Has anyone run into this the past 2 weeks?

    Monday, September 26, 2016 5:16 AM

All replies

  • User222659 posted

    Yes! I got the same issue after upgrading to iOS10.

    I checked that library (C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.Messaging.Tasks.dll) with reflector, and that class is under another namespace!

    Instead of inside the namespace "Xamarin.Messaging.Tasks" is is inside the "Xamarin.iOS.Tasks" namespace.

    Assembly Xamarin.Messaging.Tasks, Version

    They forgot to rename the namespace :(

    Tuesday, November 8, 2016 5:24 PM
  • User222659 posted

    Ok, fast fix.. while waiting for an official one.

    open: C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.After.targets

    at the top of the script, change:

    <UsingTask TaskName="Xamarin.Messaging.Tasks.CreateArchiveDirectory" AssemblyFile="Xamarin.Messaging.Tasks.dll" />

    with this:

    <UsingTask TaskName="Xamarin.iOS.Tasks.CreateArchiveDirectory" AssemblyFile="Xamarin.Messaging.Tasks.dll" />

    and recompile :)

    Tuesday, November 8, 2016 5:34 PM
  • User104720 posted

    Magic73, you workaround works. Thanks! Now waiting for fix from Xamarin team...

    Wednesday, November 9, 2016 12:33 PM
  • User76306 posted

    Have anybody filled a bug report for this issue? Here you go: https://bugzilla.xamarin.com/show_bug.cgi?id=52522

    Wednesday, February 15, 2017 12:05 PM