Bug 34877 - The "LinkAssemblies" task failed unexpectedly
Summary: The "LinkAssemblies" task failed unexpectedly
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Pre-release ()
Version: 5.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Radek Doulik
URL:
Depends on:
Blocks:
 
Reported: 2015-10-14 15:32 UTC by Mukesh Kumar Mishra
Modified: 2017-06-28 11:48 UTC (History)
7 users (show)

Tags: BZCU
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Mukesh Kumar Mishra 2015-10-14 15:32:24 UTC
When i am trying to re-build my application in release mode. Xamarin throws below error.

Error	65	The "LinkAssemblies" task failed unexpectedly.
Xamarin.Android.XamarinAndroidException: error XA2006: Reference to metadata item 'System.Runtime.Versioning.FrameworkName' (defined in 'Microsoft.Build.Tasks.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') from 'Microsoft.Build.Tasks.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be resolved. ---> Mono.Cecil.ResolutionException: Failed to resolve System.Runtime.Versioning.FrameworkName
   at Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference)
   at MonoDroid.Tuner.MonoDroidMarkStep.MarkType(TypeReference reference)
   at Mono.Linker.Steps.MarkStep.MarkField(FieldReference reference)
   at Mono.Linker.Steps.MarkStep.InitializeFields(TypeDefinition type)
   at Mono.Linker.Steps.MarkStep.InitializeType(TypeDefinition type)
   at Mono.Linker.Steps.MarkStep.InitializeAssembly(AssemblyDefinition assembly)
   at Mono.Linker.Steps.MarkStep.Initialize()
   at Mono.Linker.Steps.MarkStep.Process(LinkContext context)
   at Mono.Linker.Pipeline.Process(LinkContext context)
   at MonoDroid.Tuner.Linker.Process(LinkerOptions options, LinkContext& context)
   at Xamarin.Android.Tasks.LinkAssemblies.Execute()
   --- End of inner exception stack trace ---
   at Xamarin.Android.Diagnostic.Error(Int32 code, Exception innerException, String message, Object[] args)
   at Xamarin.Android.Tasks.LinkAssemblies.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()	Tensing.Mojave.MobileApp.Droid
Comment 1 Mukesh Kumar Mishra 2015-10-14 16:30:09 UTC
When i am trying to right click on project and export apk then again visual studio throwing below error:

Unexpected error  Reason: System.IO.FileNotFoundException: Could not load assembly 'Microsoft.Synchronization.ClientServices, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
Comment 2 Ashley Gazich [MSFT] 2015-10-15 13:37:53 UTC
Mukesh,

When you have an opportunity, would you mind providing the following additional information to help us investigate, please?

1. Reproduction sample
2. Complete build output: Visual Studio: View > Output > Show output from: Build
3. Version information: Visual Studio: Help > About Microsoft Visual Studio > Copy Info [button]

Thank you!
Comment 3 Adam Hartley [MSFT] 2017-06-28 11:48:33 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!