Hi,
As reported here:
https://support.abp.io/QA/Questions/1543/Bugs--Issues-v44X
https://support.abp.io/QA/Questions/2109/VoloAbpAbpException-Undefined-permission
It seems like ABP Suite is currently broken with Blazor Server and client. We have a new project that was supposed to have started up yesterday but since we can't even create and run a fresh project in ABP Suite currently, it is still at a standstill. We would like some information about the status on this and possible solutions / work arounds. Thanks.
Initial post fron the bug thread for 4.4.4 but not sure if anyone is reading that as there are no replies there yet.
ABP Framework version: v4.4.4 UI type: Blazor Server DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no
After upgrading to ABP 4.4.4 we can no longer create working projects in ABP Suite (have no tried other methods). The DBMigrator runs fine on a newly created project (default options, .net 5, no preview) but at runtime we get
[17:46:09 INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement
[17:46:10 WRN] Unhandled exception rendering component: Undefined permission: Audit Volo.Abp.AbpException: Undefined permission: Audit
and in the browser:
blazor.server.js?_v=637706942980000000:21 [2021-11-10T16:46:09.985Z] Error: There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.
We have also since last time we tried using ABP Suite upgraded from VS2022 Preview to Current, but I don't think that is the cause of the problem here. Could possibly be related to .net updates also.
There is additional information in the 4.4.4 bug thread linked above.
15 Answer(s)
-
1
For some strange reason, we notice that the error messages seem to be truncated. Like:
[12:12:58 WRN] Unhandled exception rendering component: Undefined permission: IdentitySe
[2021-11-12T10:57:31.733Z] Error: Volo.Abp.AbpException: Undefined setting: Volo.Abp.LeptonTheme.Layout.MenuSta
[2021-11-12T11:17:40.335Z] Error: Volo.Abp.AbpException: Undefined permission: Saas.T�
Instead of IdentityServer and MenuStart etc. Please note that it is only the first row of the error message that is truncated, stack trace etc is printed out as it should, as in:
[2021-11-12T10:57:31.733Z] Error: Volo.Abp.AbpException: Undefined setting: Volo.Abp.LeptonTheme.Layout.MenuSta at Volo.Abp.Settings.SettingDefinitionManager.Get(String name) at Volo.Abp.Settings.SettingProvider.GetOrNullAsync(String name) at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.LeptonSettingsProvider.GetMenuStatusAsync() 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()
if it isn't only the error messages but rather the code itself, it seems reasonable that it wont find the settings, permissions etc.
-
0
Can also add that doing the same thing as we tried to to in Blazor with a MVC project instead works perfectly including code generation for additional entities etc. So problems seem to be related to Blazor, but specific to the ABP Suite generated projects as the ones generated on your website works. Seems reasonable that it is the Lepthon theme perhaps that is the source of the problems, or perhaps the ABP Suite templates.
-
0
We were able to work around this by downgrading to ABP 4.4.3 (which isn't too easy to do as ABP Suite tend to go for latest packages regardless of version) as 4.4.4 just wasn't working at all with Blazor it seems.
We are a bit worried though that even though the first ticket related to these problems with Blazor and ABP 4.4.4 was created five days ago (not by us), we have yet to see an official reply from Support regarding this and it seems there are other customer affected by this as well.
-
0
please provide us the following steps to reproduce your issue
- Your ABP version:
- DB provider: EF Core / MongoDB
- Which template are you having issue? (app-pro , module-pro, console , etc..)
- Tiered or non-tiered
- UI type: Blazor Server / Blazor WASM
- Steps to reproduce the issue:
-
1
I've the same issue, more details in: https://support.abp.io/QA/Questions/2126/Error-VoloAbpAbpException-Undefined-permission-AbpId#answer-c4e31d36-4b85-a6ac-a44f-3a00363b7004
-
0
please provide us the following steps to reproduce your issue
- Your ABP version:
- DB provider: EF Core / MongoDB
- Which template are you having issue? (app-pro , module-pro, console , etc..)
- Tiered or non-tiered
- UI type: Blazor Server / Blazor WASM
- Steps to reproduce the issue:
I believe all needed information is already listed in the OP here and in other threads.
-
0
Hi @improwise, I've created an app-pro template with Blazor Server as UI and EF-Core as the database provider (in v4.4.4). Then, I could successfully generate CRUD pages for my Book entity.
- Can you check your both application version and suite version is same and in v4.4.4?
For some strange reason, we notice that the error messages seem to be truncated.
Yes, I reproduced this problem using VS 2022. But there is not any problem, when using
dotnet runcommand or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks. -
0
be sure that you have installed ABP Suite v4.4.4
-
0
Hi @improwise, I've created an app-pro template with Blazor Server as UI and EF-Core as the database provider (in v4.4.4). Then, I could successfully generate CRUD pages for my Book entity.
- Can you check your both application version and suite version is same and in v4.4.4?
For some strange reason, we notice that the error messages seem to be truncated.
Yes, I reproduced this problem using VS 2022. But there is not any problem, when using
dotnet runcommand or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks.Glad to see this issue getting some attention now and hopefully it would then be solved quickly.
Even if it works outside of Visua Studio, that isn't really a viable solution to the problem at hand here but it might give some valuable information to what needs to be fixed. Please note that after downgrading to 4.4.3, everything seems to be back to normal, we tried that ourselves to try to decide if ABP or VS/.net was the problem here. I would imagine that perhaps ABP Suite can still generate CRUD pages, we never tried that since the solution produced by ABP Suite did not work at all reliably.
-
0
be sure that you have installed ABP Suite v4.4.4
To us, that didn't make a difference as ABP Suite will use latest packages regardless. What we had to do was to create the solution manually using the CLI and specifying the version as 4.4.3, and then add it manually to ABP Suite.
I would imagine that you probably do not need to downgrade ABP Suite and CLI to 4.4.3 if you only make sure to reference 4.4.3 packages instead of 4.4.4, but we never tried that. My guess is that the Lepthon theme in 4.4.4 is causing these problems but once we got 4.4.3 to work, we have not done any more error searching.
For anyone struggling with this, you need to use the CLI like (written from memory so could be errors)
abp new myproject -t abp-pro -u blazorXXX -v 4.4.3
which would create a new project an reference 4.4.3 packages instead (ABP Suite will always use latest packages it seems regardless of version when you create the project from there). Then you can add that to ABP Suite and use it as normal and it will compile fine with both VS2019 and VS2022 and also work runtime. At least it did for us.
I hope you manage to find a solution to this quickly. Thanks.
-
0
Pls ensure that your ABP version and your project version is the same! Because we couldn't reproduce the issue.
Note that detailed reproduce steps is always helpful for the solution.
-
0
Pls ensure that your ABP version and your project version is the same! Because we couldn't reproduce the issue.
Note that detailed reproduce steps is always helpful for the solution.
Note sure what you could not reproduce as you colleague said above that he/she could reproduce it and several other customers have confirmed having the same problems as us with 4.4.4?
We have already downgraded everything to 4.4.3 ourselves currently which is working fine.
-
0
I've read the thread and couldn't find the message that successfuly reproduced the issue. @EngincanV stated that he could successfully created an entity without any problem.
Then, I could successfully generate CRUD pages for my Book entity.
Again detailed reproduce steps is always helpful for the solution.
-
0
I've read the thread and couldn't find the message that successfuly reproduced the issue. @EngincanV stated that he could successfully created an entity without any problem.
Then, I could successfully generate CRUD pages for my Book entity.
Again detailed reproduce steps is always helpful for the solution.
Yes, I reproduced this problem using VS 2022. But there is not any problem, when using dotnet run command or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks.
The problem here is that the solutions produced by ABP Suite 4.4.4 won't build in VS2019 and won't run in VS2022. And based on what is written here in the support forum, several customers are experiencing the same problem(s). All the information needed to reproduce this problem is already available in the forum and we have already sent you a SLN produced by ABP Suite that shows the problem.
We seem to be stuck in a discussion if the problem(s) exist(s) or not and not moving closer to a solution to them...
Edit: I see that a 5.0 RC1 just got released which is reported to work with VS2022, hopefully those fixes will transition to the 4.4 branch as well.
-
0
Hi @improwise,
As i see, the issue is resolved. Right?
