We are getting the following exception when redirecting to the login page after we updated to 5.3.0. Everything works fine locally but not when deployed to Azure.
We need some feedback on this ASAP since we were going to go live this weekend.
BSR.Beinni.IdentityServer terminated unexpectedly!
Volo.Abp.AbpInitializationException: An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module BSR.Beinni.BeinniIdentityServerModule, BSR.Beinni.IdentityServer, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: The type 'qgApoZ2OmDdJqiAoXp5.L4ObZ82mStp54vqoB0A' is not a valid page. A page must define a public, non-static 'Model' property.. See the inner exception for details.
---> System.InvalidOperationException: The type 'qgApoZ2OmDdJqiAoXp5.L4ObZ82mStp54vqoB0A' is not a valid page. A page must define a public, non-static 'Model' property.
here is the whole error in an image
There seems to be a similar unanswered issue (since 9 months) here A page must define a public, non-static 'Model' property
- ABP Framework version: v5.3.0
- UI type: MVC / Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes
5 Answer(s)
-
0
Is this the same issue as this one https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error ?
-
0
Yes, I have the same issue. I cannot deploy anymore.
I don't know what's causing the issue? Is it an entity naming issue? I have some entities ending in 01, 02, 03, 04 which caused problems with swagger and generated .js code.
My app is too big to create a new version, and move the code from the current app to a new one with the same name.
I did this once before, more than a year ago, which allowed me to co continue. I have copied all my entities to .\aspnet-core.suite\entities and creating the basic CRUDS and Pages to test deploys.
This may be a futile exercise, but may point to the problem.
I have already run into a AppUser navigations problem. I can't link Employees to an AppUser system account.
Good luck, all the best.
-
0
Hi @Sturla
We're aware of the problem and almost solved it. It'll be released in a patch version.
Thanks for your patience.
Also your credit is refunded.
-
0
For others.. still an issue after updating to 5.3.1
-
0
Please add your issues here if you are facing any issues after 5.3.1 updatehttps://support.abp.io/QA/Questions/3364/ABP-v531-Problems
