MudBlazor.BrowserViewportService - DisposeAsync when using Azure Feature Flags

[tsmccartan]

I have an implemented Blazor App using Mud Blazor, and am implementing Feature Flags, based on Azure App Configuration. This works and I can get the Features. I am following this example to be able to create a custom component to enable/disable Components/Menu Items based on a Component (Similar to Built in ASP.NET Core Features).

https://dev.to/kasuken/how-to-use-feature-flags-in-a-blazor-application-1ni6

But implementing this causes the following error:

System.InvalidOperationException: 'MudBlazor.BrowserViewportService' type only implements IAsyncDisposable. Use DisposeAsync to dispose the container.

I am wondering if this is a similar issue from the discussion here:
#7879

I can't control the MudBlazor.BrowserViewportService so I don't know how to get around this.

FYI, in my Razor Component, I can get the Feature Flag, and use an @if then with a model variable and that works, but it is not as elegant as a component attribute.

Home @if (_COUNTER_FEATURE) { Counter } Weather

    protected override void OnInitialized()
    {
        _COUNTER_FEATURE = _featureManager.IsEnabledAsync("Counter").Result;

        base.OnInitialized();
    }

Thanks,
Tom

[ScarletKuro]

I am wondering if this is a similar issue from the discussion here:
#7879

Yes, they are related.

I can't control the MudBlazor.BrowserViewportService so I don't know how to get around this.

You can implement own IBrowserViewportService and replace the default registration of that type in the container. However, you will get exception with other services that only implement IAsyncDisposable. The BrowserViewportService is just first to throw.
Since no one could provide me a reproduction repository #7879 (comment) I couldn't send the bug report to MS so they fix it for .net8 at least. For now it seems like we need to wait for .NET9 where this is fixed.