- ABP Framework version: v5.1.3
- UI type: Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
Hello after update to 5.1.3 versión, the BlazorWasm not found.
The issue showing in browser is:
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: WebAssemblyCachedApplicationConfigurationClient should be initialized before using it. Volo.Abp.AbpException: WebAssemblyCachedApplicationConfigurationClient should be initialized before using it. at Volo.Abp.AspNetCore.Components.WebAssembly.WebAssemblyCachedApplicationConfigurationClient.GetConfigurationByChecking() at Volo.Abp.AspNetCore.Components.WebAssembly.WebAssemblyCachedApplicationConfigurationClient.Get() at Volo.Abp.AspNetCore.Mvc.Client.RemoteLocalizationContributor.GetResourceOrNull() at Volo.Abp.AspNetCore.Mvc.Client.RemoteLocalizationContributor.GetOrNull(String cultureName, String name) at Volo.Abp.Localization.LocalizationResourceContributorList.GetOrNull(String cultureName, String name) at Volo.Abp.Localization.AbpDictionaryBasedStringLocalizer.GetLocalizedStringOrNull(String name, String cultureName, Boolean tryDefaults) at Volo.Abp.Localization.AbpDictionaryBasedStringLocalizer.GetLocalizedString(String name, String cultureName) at Volo.Abp.Localization.AbpDictionaryBasedStringLocalizer.GetLocalizedString(String name) at Volo.Abp.Localization.AbpDictionaryBasedStringLocalizer.get_Item(String name) at Volo.Abp.UI.Navigation.DefaultMenuContributor.Configure(MenuConfigurationContext context) at Volo.Abp.UI.Navigation.DefaultMenuContributor.ConfigureMenuAsync(MenuConfigurationContext context) at Volo.Abp.UI.Navigation.MenuManager.GetInternalAsync(String name) at Volo.Abp.UI.Navigation.MenuManager.GetAsync(String[] menuNames) at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.Navigation.MainMenuProvider.GetMenuAsync() at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.MainHeader.MainHeader.OnInitializedAsync() at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync() global.js:249:35461
- Steps to reproduce the issue:"
After I updated my solution to 5.1.3
Thank you,
3 Answer(s)
-
0
Hi @jhsanc I've made my checks and couldn't catch the same error with that.
Have you checked the Migration Guides and applied them properly?
If yes, which version did you update from?
-
1
Hello finding in google a solution, I found this:
https://tagmerge.com/issue/abpframework/abp/11364
The solution offered by Lian found.
Then please close this issue.
Thank you,
-
0
I am closing the question since your problem seems resolved with this issue. Thanks @jhsanc