Starts in:
2 DAYS
4 HRS
31 MIN
8 SEC
Starts in:
2 D
4 H
31 M
8 S

Activities of "neethucp"

The configuration is added in Blazor Server module as we want to use Azure SignalR for blazor.

The application works properly if we remove the line "context.Services.AddSignalR().AddAzureSignalR();" and all menu items are displayed correctly.

Hi,

We are not building a chat application. We just added the azure signalR configuration context.Services.AddSignalR().AddAzureSignalR(); in blazor module and the connection string in appsettings.

https://custman-my.sharepoint.com/:v:/g/personal/aoomm_lighthousehq_com_au/EchOgOpX4oRJtj6NaBwqKKgB5xT9iByJUwjru6xYN10AmQ?e=8lUdPw

Menu items are disappearing when we use azure signalR in blazor server app and only the "Home" menu appears. If we remove the permission for other menu items, those get displayed. We were able to reproduce the issue in a new abp project.

  • ABP Framework version: v7.2.2
  • UI type: Blazor Server
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes

We are getting the following error when trying to intergrate Azure SignalR to our exisitng blazor server application.

System.NullReferenceException: Object reference not set to an instance of an object. [blazor_f49e0680-3]: at Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.SideMenu.Navigation.MobileNavbar.BuildRenderTree(RenderTreeBuilder __builder) [blazor_f49e0680-3]: at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException).

Please help to fix the issue.

  • ABP Framework version: v7.2.2
  • UI type: Blazor Server
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes

That fixed the issue. Thank you.

Hi, we have added the automapping for elsa dashboard manually. And the dashboard issue is sorted. But major issue we are facing is with workflow instance not getting updated. Following is the code in elsa to save the instance. On debugging we found that entity is in detached state and hence change tracking not working for update. https://github.com/elsa-workflows/elsa-core/blob/392b4509217bf1c2b8c90a4ed669bc71ab45f4ab/src/persistence/Elsa.Persistence.EntityFramework/Elsa.Persistence.EntityFramework.Core/Stores/EntityFrameworkStore.cs

We have integrated elsa workflow to abp project. It was all working fine with abp v7.0.3. But when we updated abp to version 7.1 following issues started happening

  1. Unable to access elsa dashboard api's as automapper mappings configured in elsa package stopped working.
  2. Elsa workflow instances doesn't save properly when updated, as entity change tracking doesn't work. Elsa gets the entity from the database and maps the latest changes to the entity using automapper and then saves the dbcontext. But the entity is in detached state after mapping and hence changes not saved.

Can you please shed some light on what changed with the version 7.1 that might be causing this issue. Elsa is also using .net 7 and automapper version 12.0.0.

  • ABP Framework version: v7.1
  • UI type: Blazor
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes

Hi, I'm getting the token in the Authorization header. But I'm still getting unauthorized.

Hi, The issue was due to the incorrect signalR url. The url didn't have the hub name in kebab-case. It started working after url changed to "/signalr-hubs/application-status-change-notification". But now getting issue with authorization. The token is getting passed in Authorization header, but signalR negotiation gives the following error.

Showing 31 to 40 of 44 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06