This message was deleted.

I seem to have found out the problem, writing an issue now since it (probably) requires a fix in the dotnet SDK