Open Closed

Easy-CRM Blazor stops working after login #910

User avatar
0
Jurjen created
  • Steps to reproduce the issue:

I have downloaded the easy-crm Sample application. Unzipped, followed the steps as explained on this page: https://docs.abp.io/en/commercial/latest/samples/easy-crm

Then I open the solution and run Volo.EasyCrm.Web, I log in to that application, then from VS-2019 I start the Volo.EasyCrm.Blazor project, The login page appears, I log in, then the screen goes gray and the nice 'C' keeps rotating.... that's where things stop working.

I have searched the docs / samples / support forum couldn't find a solution there.

I'm not sure what going wrong but this is one of the warnings I get.

** Could not find IdentityClientConfiguration for . Either define a configuration for  or set a default configuration.

And then at the end there's this Exception: Unhandled exception rendering component: VTable setup of type Blazorise.Snackbar.SnackbarStack failed

  • ABP Framework version: v4.0.0-rc3 (as in the easy-crm.zip, I've tried upgrading the Volo.Abp packages to 4.2.1 but the fails in vs-2019 every time)
  • UI type: MVC / Blazor
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): Tiered (MVC)
  • Exception message and stack trace:

The MVC application is working just fine, but the Blazor application is failing.

Can anyone shed some light on this problem ?

Kind regards, Jurjen

--- Debug output ---


info: System.Net.Http.HttpClient.AbpMvcClient.LogicalHandler[101]
      End processing HTTP request after 179.9099ms - 200
'iisexpress.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App\5.0.3\Microsoft.AspNetCore.Metadata.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
warn: Volo.Abp.IdentityModel.IdentityModelAuthenticationService[0]
      Could not find IdentityClientConfiguration for . Either define a configuration for  or set a default configuration.
info: System.Net.Http.HttpClient.AbpMvcClient.LogicalHandler[100]
      Start processing HTTP request GET https://localhost:44338/api/abp/application-configuration?api-version=1.0
info: System.Net.Http.HttpClient.AbpMvcClient.ClientHandler[100]
      Sending HTTP request GET https://localhost:44338/api/abp/application-configuration?api-version=1.0
info: System.Net.Http.HttpClient.AbpMvcClient.ClientHandler[101]
      Received HTTP response headers after 50.8899ms - 200

info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
      Authorization failed. These requirements were not met:
      PermissionRequirement: EasyCrm.Countries
: /__w/1/s/src/mono/mono/metadata/loader.c:1964 <disabled>
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: VTable setup of type Blazorise.Snackbar.SnackbarStack failed
System.TypeLoadException: VTable setup of type Blazorise.Snackbar.SnackbarStack failed
   at System.Reflection.RuntimeConstructorInfo.InternalInvoke(Object obj, Object[] parameters, Boolean wrapExceptions)
   at System.RuntimeType.CreateInstanceMono(Boolean nonPublic, Boolean wrapExceptions)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean wrapExceptions, Boolean skipCheckThis, Boolean fillCache)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, Boolean wrapExceptions)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic, Boolean wrapExceptions)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.Activator.CreateInstance(Type type)
   at Blazorise.ComponentActivator.CreateInstance(Type componentType)
   at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(IServiceProvider serviceProvider, Type componentType)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateComponent(Type componentType)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame& frame, Int32 parentComponentId)
   at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewComponentFrame(DiffContext& diffContext, Int32 frameIndex)
   at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& diffContext, Int32 frameIndex)
   at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& diffContext, Int32 newFrameIndex)
   at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
   at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: No element is currently associated with component 12
      Error: No element is currently associated with component 12
          at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
          at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
          at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
          at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
          at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
          at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
          at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
          at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
          at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
          at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 12
Error: No element is currently associated with component 12
    at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
    at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
    at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
    at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
    at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
    at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
    at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
    at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
    at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
    at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object,Object](String identifier, Int32 arg0, RenderBatch arg1, Object arg2, Int64 targetInstanceId)
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object](String identifier, Int32 arg0, RenderBatch arg1)
   at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.UpdateDisplayAsync(RenderBatch& batch)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: No element is currently associated with component 18
      Error: No element is currently associated with component 18
          at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
          at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
          at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
          at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
          at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
          at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
          at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
          at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
          at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
          at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 18
Error: No element is currently associated with component 18
    at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
    at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
    at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
    at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
    at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
    at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
    at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
    at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
    at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
    at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object,Object](String identifier, Int32 arg0, RenderBatch arg1, Object arg2, Int64 targetInstanceId)
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object](String identifier, Int32 arg0, RenderBatch arg1)
   at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.UpdateDisplayAsync(RenderBatch& batch)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
      Authorization failed. These requirements were not met:
      DenyAnonymousAuthorizationRequirement: Requires an authenticated user.
info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
      Authorization failed. These requirements were not met:
      DenyAnonymousAuthorizationRequirement: Requires an authenticated user.
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: No element is currently associated with component 5
      Error: No element is currently associated with component 5
          at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
          at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
          at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
          at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
          at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
          at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
          at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
          at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
          at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
          at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 5
Error: No element is currently associated with component 5
    at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
    at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
    at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
    at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
    at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
    at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
    at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
    at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
    at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
    at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object,Object](String identifier, Int32 arg0, RenderBatch arg1, Object arg2, Int64 targetInstanceId)
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object](String identifier, Int32 arg0, RenderBatch arg1)
   at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.UpdateDisplayAsync(RenderBatch& batch)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: No element is currently associated with component 5
      Error: No element is currently associated with component 5
          at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
          at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
          at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
          at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
          at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
          at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
          at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
          at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
          at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
          at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 5
Go to accepted answer
8 Answer(s)
  • User Avatar
    0
    cotur created

    Hi @Jurjen,

    The downloaded version is old and we will update it asap. I'll write here again when we upload the latest version.

  • User Avatar
    0
    Jurjen created

    Hi @Jurjen,

    The downloaded version is old and we will update it asap. I'll write here again when we upload the latest version.

    Hi Cotur,

    Looking forward to that! Do you have any indication when this new version will be available ?

    Jurjen

  • User Avatar
    0
    alper created
    Support Team Director

    @Jurjen we'll send you the patch version (from DEV branch). I'll contact you via email

  • User Avatar
    0
    Jurjen created

    Thanks for the download link, going to check it rightaway

  • User Avatar
    0
    alper created
    Support Team Director

    did you add your private NuGet source to the NuGet.config file? you can find your private NuGet address from your existing project.

  • User Avatar
    0
    Jurjen created

    Hi Alper,

    Yes I did add our private Nuget address to the nuget.config. But in the appsettings.json there’s this line :

    "AbpLicenseCode": "{PUT_YOUR_LICENSE_CODE_HERE}"

    If I leave it in the file like that the app won’t start and leaves this message in the log file:

    2021-02-26 09:43:29.782 +01:00 [ERR] ABP-LIC-0020 - License code not found! Ensure that your appsettings.json has "AbpLicenseCode" key with your license code. 2021-02-26 09:43:29.782 +01:00 [ERR] ABP-LIC-0008 - License check failed for 'Volo.Abp.Identity.Pro.HttpApi-v4.2.0.0'.

    If I put our GUID in the AbpLicenseCode the app won’t start either and leaves a similar message in the log file. So I guess the GUID is not the license key. Where can we find the license key because we can't seem to find it on the page where out secret nuget url is.

  • User Avatar
    0
    alper created
    Support Team Director

    You confused AbpLicenseCode and NuGet addresses. I also see that you are sending email about this issue. Please go with 1 channel.

    You can find your AbpLicenseCode in your existing appsettings.json files. You can find your NuGet source in your existing NuGet.config files.

    so copy them from your existing project into this new project. that's it.

  • User Avatar
    0
    Jurjen created

    It works now, thank you for your support !

Assignee
User avatar cotur
Labels
Non yet
Made with ❤️ on ABP v8.2.0-preview Updated on March 25, 2024, 15:11