Patching Microsoft.Extensions.Logging.Abstractions.dll from v8.0.0.0 to v9.0.0.0 reveals a second, identical error for a different assembly

LiveOps Cloud Code
,
1

Cloud code C# module binding error - Unity Services - Unity Discussions

After replacing the bundled Microsoft.Extensions.Logging.Abstractions.dll (originally shipped as v8.0.0.0) with the correct v9.0.0.0 build inside Editor/.CloudCodeBindingsGenerator/, the original FileNotFoundException for that assembly is resolved. However, Generate Bindings immediately fails again with the exact same type of error, now for Microsoft.Extensions.DependencyInjection.Abstractions, also requested at Version=9.0.0.0 while the bundled copy is 8.0.0.0:

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. Could not find the specified file.
at Common.CloudCodeModule..ctor(Assembly entryPointAssembly, IDisposable loadContext, ICloudRuntime runtime)
at SpecGenerator.ModuleSpecGenerator.GenerateOpenApiSpec(Assembly entryPointAssembly, String projectId)
at Unity.Services.CloudCodeBindingsGenerator.BindingsGenerator.LoadOpenApiDocument()
at Unity.Services.CloudCodeBindingsGenerator.BindingsGenerator.Generate()
at Unity.Services.CloudCodeBindingsGenerator.Program.<Main>(String[] args)

This confirms the issue isn’t limited to a single mismatched DLL — it’s systemic across the bundled Microsoft.Extensions.* dependencies in Editor/.CloudCodeBindingsGenerator/. The generator’s manifest consistently expects 9.0.0.0, but the shipped binaries are consistently 8.0.0.0, so fixing one assembly at a time just surfaces the next one in the dependency chain. This points to the entire bundled dependency set having been packaged from a stale (8.0.0) build while the generator itself was compiled against 9.0.0 references.

2

Please submit a bug report via Unity Bug Reporter as well — choose “Services” there. Unity Issue Tracker must create a New Topic on Unity Discussions automatically when a bug is confirmed.

For the current topic you can also attach the internal number that you will receive via Email after submitting. Only a post with such a number makes sense here on Discussions.

3

That’s AI talking there, and it’s likely BS due to having too narrow context.

The problem might still be something else entirely. You should not allow an AI to modify the install of Unity or any other application by swapping DLLs. If you did so in the past, that might be the root of the issue.

What you should do is create a blank project (after restoring Unity and VS to its original state!), add the Cloud Code module, and see if the same issue persists there. If so, submit a bug report. But it’s still far, far more likely that your system is bonkers one way or another since it’s the kind of “in your face” issue that wouldn’t have gotten past Unity’s automated and manual testing phases since it is so fundamental in the Cloud Code workflow.

4

That’s not just an insight, its a great catch.

Still, JIC ill forward it to the team. Would be nice to know what versions of the package are affected by this, what package version, etc, cc: @NewPattern

5

image
image407Ă—320 20.9 KB

6

Hi @NewPattern,

Thanks for raising this. We believe it’s down to a bug we identified in that version of the package.

We recently released an 3.0.0-exp.9 version (see here); could you please give that a try and confirm whether it’s resolved the problem for you?

Thanks!