.netcore 3.1 builds broken as of 30/06/2022
See original GitHub issueGoogle cloud build no longer working as of 30/06/2022 for .netcore 3.1 I tested an old working build and got the same error so it is not a code change causing this
It now outputs this error
Build failed: Failed to run /bin/build: couldn't find runtime version from runtimeconfig.json: &dotnet.RuntimeConfigJSON{RuntimeOptions:dotnet.runtimeOptions{TFM:"netcoreapp3.1", Framework:dotnet.framework{Name:"Microsoft.NETCore.App", Version:"3.1.0"}, Frameworks:[]dotnet.framework(nil), ConfigProperties:dotnet.configProperties{SystemGCServer:false}}}; Error ID: b1205d15
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:13 (10 by maintainers)
Top Results From Across the Web
.NET Core 3.1 will reach End of Support on December 13, ...
NET Core 3.1 will reach end of support on December 13, 2022, this blog breaks down all the valuable information you need to...
Read more >.Net Core Updating to 3.1.31 from 3.1.5 - Internal Server ...
On installing the ASP Net Core runtime (1) the site broke, then I installed the dotnet-runtime (2) and the site came back up...
Read more >Install dotnet-sdk-3.1 on WSL with Ubuntu 20.04 tells me " ...
I get an error saying I have broken packages. I am on. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04...
Read more >Net Core/MSBuild Tooling not finding right version
Error : Version 3.1.401 of the .NET Core SDK requires at least version 16.7.0 of MSBuild. The current available version of MSBuild is...
Read more >Blog
In theory, always using the latest version of .NET Core SDK should work, but if your build was broken or you are in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Current simplified version that still demonstrates the problem:
Platforms
element in the dependencyEmbeddedResourceUseDependentUponConvention
element in the dependencyIHttpFunction
(because that’s easier to test)I’ll keep looking either later today or tomorrow. (I’m travelling again today I’m afraid.) But this is definitely progress…
I’m going to close this issue now, as the buildpacks repo is the right place to fix this - but please do add any comments (either here or on that issue) if you have additional insights/restrictions.