[BUG] FSH.BlazorWebAssembly.Client.Shared.BaseLayout.SetCurrentTheme - Null Ref while using Azure Auth about blazor-wasm-boilerplate HOT 6 CLOSED

There might be a bug somewhere how that null value got there in the first place (if it's not from doing some strange debugging stuff), but has nothing to do with AzureAd... ;-)

from blazor-wasm-boilerplate.

And that error message is probably fine... I think the signalr client always probes first without credentials, and only sends them after a 401 received.

from blazor-wasm-boilerplate.

I don't see this problem. What are the exact steps to reproduce? Seems to be something with your themepreference? This is something that's stored in local storage. Maybe it still has some stale data from previous versions?

from blazor-wasm-boilerplate.

steps:

1. deleted db,
2. insert value for Issuer into Tenant eg https://sts.windows.net/...
3. set provider to azure on both api and wasm,
4. run api host
5. run wasm

exception shown once log-in negotiations completed
exception shown once log-out completed

from blazor-wasm-boilerplate.

Have you checked your local storage? I bet there's a null value there somewhere in your themepreference which shouldn't be there...

from blazor-wasm-boilerplate.

yeah - that was it - working ok now. I do get another exception - but I should probably close this and raise another.

from blazor-wasm-boilerplate.