Hi ABP Support,
I have been working on ABP Blazor UI with Separated Identity Server at version 3.3.0:
- Blazorised components are all okay.
- Hooking Blazor UI up to back-end app services is all right to some extent, but it throws stack overflow exception on 1 particular app service (see details below)
- Emptying the app service to literally make it do as little as possible does not help
- The error still occurs
- It takes roughly longer than 5 minutes to throw the exception
- Not exposing the app service fixes the issue, but this is not I need
- I need the Blazor UI to use the app service as per ABP BookStore sample app
- Emptying the app service to literally make it do as little as possible does not help
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/
- No relavant info
Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index
- No relavant info
The exact solution to your question may have been answered before, please use the search on the homepage.
- ABP Framework version: v3.3.0
- UI type: Blazor
- Tiered (MVC) or Identity Server Seperated (Angular): yes
- Exception message and stack trace:
- please be advised that I do NOT have D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Http.Client\Volo\Abp\Http\Client\DynamicProxying\ApiDescriptionFinder.cs
- please be advised that I even do NOT have D drive :(
- Steps to reproduce the issue:
- Just follow the normal ABP project start-up:
- run DbMigrator
- run IdentityServer
- run HttpApiHost
- run Blazor
Not exposing the app service fixes the issue, but I cannot use the app service on Blazor UI:
Other app services look okay though :(
7 Answer(s)
-
0
Hi,
Can you share your
application servicesandblazorcode? -
0
Hi @liangshiwei,
How are you?
You possibly have been busy with 4.0.0 release recently.
I am just wondering if you have had any chance to read through my last email and possibly give me some hints to move forward please.
Many thanks and Best regards.
-
0
updating to the latest version may fix it. go to this URL and write us the response
api/abp/api-definition/ -
0
Hi @alper,
thanks for your advice.
we are in the middle of upgrading our apps to ABP 4.0.0, and apprarently have to upgrade it to 4.0.1 now, but it looks like the latest version still has some issues with Angular. We have created multiple brand-new projects (again and again) and all new Angular apps cannot start
- looks like the error is from angular-oauth2-oidc
- we debugged the new Angular apps on front-end
now we might need to wait for your 4.1 release to get all Angular and Blazor and back-end to work well I guess
in the mean time, I still have issues with Blazor and Swagger API as mentioned above, but I will read through your implementation on File Management module at v4.0.1 to follow your convention for now
-
0
Hi,
We have fixed this problem, you can upgrade to 4.0.2 version.
-
0
thanks @liangshiwei.
we will upgrade our apps to ABP v4.0.2 asap and get back to you and @alper shortly
-
0
Guys I realized that the below package is used in the Blazor project
Microsoft.AspNetCore.Components.WebAssembly.DevServerBefore you publish your project, change this package to the below one
Microsoft.AspNetCore.Components.WebAssembly.ServerI guess the second one provides more performance, the first one is for development (hot reload, rebuild on change, etc...)
