Unable to deploy function using .NET Core SDK 5.0.102 on Big Sur 11.1

Description

When attempting to deploy a serverless ASP.NET Core Lambda function using dotnet lambda deploy-serverless, the CLI tool fails with an MSBuild error and the dotnet application crashes.

Could not load file or assembly 'System.Net.Primitives, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. A device attached to the system is not functioning.

This occurs when using the .NET Core SDK 5.0.102 on macOS Big Sur 11.1. Note: Downgrading to .NET Core SDK 3.1.405 resolves the issue.

Reproduction Steps

1. Create a new blank serverless ASP.NET Core Lambda function.
2. Attempt to deploy the function using dotnet lambda deploy-serverless using Terminal.
3. The error below is thrown in the output.

Logs

... publish: MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.
... publish: Microsoft.Build.BackEnd.NodeFailedToLaunchException: Could not load file or assembly 'System.Net.Primitives, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. A device attached to the system is not functioning.
... publish:  (0x8007001F)
... publish:  ---> System.IO.FileLoadException: Could not load file or assembly 'System.Net.Primitives, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. A device attached to the system is not functioning.
... publish:  (0x8007001F)
... publish: File name: 'System.Net.Primitives, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
... publish:    at System.Diagnostics.Process.OpenStream(Int32 fd, FileAccess access)
... publish:    at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
... publish:    at System.Diagnostics.Process.Start()
... publish:    at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
... publish:    at Microsoft.Build.BackEnd.NodeProviderOutOfProcBase.LaunchNode(String msbuildLocation, String commandLineArgs)
... publish:    --- End of inner exception stack trace ---
... publish:    at Microsoft.Build.BackEnd.NodeProviderOutOfProcBase.LaunchNode(String msbuildLocation, String commandLineArgs)
... publish:    at Microsoft.Build.BackEnd.NodeProviderOutOfProcBase.GetNode(String msbuildLocation, String commandLineArgs, Int32 nodeId, INodePacketFactory factory, Handshake hostHandshake, NodeContextTerminateDelegate terminateNode)
... publish:    at Microsoft.Build.BackEnd.NodeProviderOutOfProc.CreateNode(Int32 nodeId, INodePacketFactory factory, NodeConfiguration configuration)
... publish:    at Microsoft.Build.BackEnd.NodeManager.AttemptCreateNode(INodeProvider nodeProvider, NodeConfiguration nodeConfiguration)
... publish:    at Microsoft.Build.BackEnd.NodeManager.CreateNode(NodeConfiguration configuration, NodeAffinity nodeAffinity)
... publish:    at Microsoft.Build.Execution.BuildManager.PerformSchedulingActions(IEnumerable`1 responses)
... publish:    at Microsoft.Build.Execution.BuildManager.HandleNewRequest(Int32 node, BuildRequestBlocker blocker)
... publish:    at Microsoft.Build.Execution.BuildManager.ProcessPacket(Int32 node, INodePacket packet)
... publish:    at Microsoft.Build.Execution.BuildManager.<>c__DisplayClass70_0.<Microsoft.Build.BackEnd.INodePacketHandler.PacketReceived>b__0()
... publish:    at Microsoft.Build.Execution.BuildManager.ProcessWorkQueue(Action action)
... publish: --- End of stack trace from previous location ---
... publish:    at Microsoft.Build.Execution.BuildManager.EndBuild()
... publish:    at Microsoft.Build.CommandLine.MSBuildApp.BuildProject(String projectFile, String[] targets, String toolsVersion, Dictionary`2 globalProperties, Dictionary`2 restoreProperties, ILogger[] loggers, LoggerVerbosity verbosity, DistributedLoggerRecord[] distributedLoggerRecords, Int32 cpuCount, Boolean enableNodeReuse, TextWriter preprocessWriter, TextWriter targetsWriter, Boolean detailedSummary, ISet`1 warningsAsErrors, ISet`1 warningsAsMessages, Boolean enableRestore, ProfilerLogger profilerLogger, Boolean enableProfiler, Boolean interactive, Boolean isolateProjects, Boolean graphBuild, Boolean lowPriority, String[] inputResultsCaches, String outputResultsCache)

Environment

• Build Version: Amazon Lambda Tools for .NET Core applications (5.0.0)
• OS Info: macOS Big Sur 11.1
• Build Environment: Visual Studio | VSCode + Terminal dotnet
• Targeted .NET Platform: .NET Core 3.1 LTS

Resolution

No resolution, only workaround is to remove SDK 5.0.102 from the system.

• 👋 I can/would-like-to implement a fix for this problem myself

---

This is a 🐛 bug-report

[smarts]

For anyone else who encounters this issue and uses ESET: I encountered this same problem and it was due to the Enable Real-time file system protection checkbox being checked in ESET.

[ashishdhingra]

Thanks @ashishdhingra.

I can confirm this does not occur on Windows 10 Version 1909 using .NET SDK Version: 5.0.102.

I agree this appears to be an issue with the .NET Core 5.0 SDK on macOS. Unfortunately, I don’t have a macOS Catalina 10.15.7 environment to test in sorry.

I will try to reproduce this on macOS Catalina and let you know the results. I’m not sure if this is AWS Lambda Tools issue though since the error occurs during MSBuild process.