CascadingAuthenticationState error

[ProjectFoxx]

Hello all,

I hope you guys can help me with this error.

I have an error when i am rendering a page. I get a CascadingAuthenticationState error:
System.InvalidOperationException : Cannot resolve scoped service 'Microsoft.AspNetCore.Components.Authorization.CascadingAuthenticationState' from root provider. How can i fix this?

I already read this: https://bunit.dev/docs/test-doubles/faking-auth.html

I already did this
using var ctx = new TestContext();
TestAuthorizationContext authContext = ctx.AddTestAuthorization();
authContext.SetAuthorized("sffsdf.fsffe.com", AuthorizationState.Authorized);
authContext.SetRoles("Administrator");

But still get this error how can i fix this?

[linkdotnet]

Hey @ProjectFoxx can you post the whole test and component?
Especially how you render your component in the test.

[ProjectFoxx]

This are the test and component

Test
public void ArticleAdd()
{
testContext.Services.AddSingleton<NavigationManager, MockedNavigationManager>();
navigationManager = testContext.Services.GetService();

        navigationManager.NavigateTo("articles");
        var articlesPage = testContext.RenderComponent<CascadingAuthenticationState>(x => x.AddChildContent<ArticlesPage>());

        var renderedMarkup = page.Markup;
        Console.WriteLine(renderedMarkup);

        page.MarkupMatches("Add");

    }

Page:

`@inject IModalService Modal
@Attribute [Authorize(Roles = "Administrator")]

@page "/articles"
@using App.Client.Configuration
@using App.Client.Modals.PurchaseOrders

StandardPageLayout>
Grid DataSource="async (start,amount) => await Api.AllArticles.Get()"
AddItem="AddArticle"
EditItem="EditArticle"/>
/StandardPageLayout>`

AddArticle()
RemoveArticle()

[linkdotnet]

Hmm my first question would be why do you try to render the CascadingAuthenticationState?

I guess so that the whole authentication kicks in. But you don't have to do that. You can just render your component all the rest does bUnit for you. So exchange that testContext.RenderComponent<CascadingAuthenticationState>(...) to this: testContext.RenderComponent<ArticlesPage>();.

Here a minimal repro for you:

The component:

@attribute [Authorize(Roles = "Administrator")]

<h2>@text</h2>

<button @onclick="@(() => text = "Hello World")">Click me</button>

@code {
    private string text = "";
}

And a test:

[Fact]
public void SomeNiceTestDescription()
{
    using var ctx = new TestContext();
    ctx.AddTestAuthorization()
        .SetAuthorized("A Username")
        .SetRoles("Administrator");
    var cut = ctx.RenderComponent<ComponentWithAuth>();

    cut.Find("button").Click();

    var h2Text = cut.Find("h2").TextContent;
    Assert.Equal("Hello World", h2Text);
}

[ProjectFoxx]

thx for your help @linkdotnet i tried normal rendering before but got the same error thats why i added CascadingAuthenticationState to the render component. So i changed it back after your feedback

I changed the code for testauthorization just like yours and changed the order of loading and now i get a different error.
So i dont have the CascadingAuthenticationState error anymore :)

Progress i guess. the new error is the following
"Authorization requires a cascading parameter of type Task<AuthenticationState>. Consider using CascadingAuthenticationState to supply this."

I guess that is a thing they have to fix in a component im using. i found this error on this website and checked our app.razor but its the same
https://www.iaspnetcore.com/blog/blogpost/5f5fa51f9122f001e4b7aa0b
So i will contact the developers of that component

Again thx for your help :)