NullReferenceException when accessing from Dependency Injection using Azure Functions about asynckeyedlock HOT 4 CLOSED

For some reason it's not able to create the instance, but you can help it, and also use the recommended parameters at the same time.

In your Startup.cs, change:

builder.Services.AddSingleton<AsyncKeyedLocker<string>>();

To:

builder.Services.AddSingleton(new AsyncKeyedLocker<string>(o =>
{
    o.PoolSize = 20;
    o.PoolInitialFill = 1;
}));

from asynckeyedlock.

I will investigate why the above may be happening but that's the workaround for now.

from asynckeyedlock.

This issue is a known issue with Azure Functions. Refer to https://stackoverflow.com/questions/57991405/dependency-injection-injecting-null-when-missing-registration-in-azure-functions and https://stackoverflow.com/questions/60379123/microsoft-extensions-dependencyinjection-injects-null-to-constructor-instead-of

As such, there is nothing we can do from our end. I will mark this as closed.

from asynckeyedlock.

Also, found out there is a GitHub issue that talks about this at Azure/azure-functions-host#8322

from asynckeyedlock.