Closed joacar closed 4 months ago
Hello @joacar!
That error is only possible in 4.0.0-preview
and above. I see 4.0.0-preview2
in your log which sounds like your app might have had the FeatureManagement package be updated to the preview version. If this wasn't intentional, you may want to go back to stable 3.2.0
.
That warning means there was no ITargetingContextAccessor
defined. This means TargetingContext
can't be automatically determined for the given user. This only matters if you're using TargetingFilters or the preview feature Variants.
Either way, us logging this warning here is misleading, it should happen only during variant assignment. So thank you for reporting it!
Thanks I'll check the version of the NuGet package so it's really 3.2.0
Hi, @joacar Did you confirm that the problem was caused by the package version?
Sorry I forgot to reply! I'm quite sure I haven't seen it, let me verify later this evening.
Cheers
Problem resolved!
@joacar Glad to hear that. I will close this issue.
Hi
In my production logs I see this warning message
No instance of ITargetingContextAccessor is available for variant assignment.
from namespaceMicrosoft.FeatureManagement.FeatureManager
.NuGet
Microsoft.FeatureManagment.AspNetCore::3.2.0
dotnet