Hello,
can you please check this similar issue https://support.abp.io/QA/Questions/3773/volodocs-set-up-error if it helps you.
Thanks
Hi Anjali
Sorry but that issue is unrelated to our issue.
Thanks
Phil
Hi Anjali
Yes I have followed that guide from start to finish, I have also tried spinning the App up using the EXE and it produces the same page.
Hi Mahmut
Is there any workaround for this issue as we are also facing it?
Thanks
Phil
Yes I have read that document but it only has replacement as an option whereas I want to retain an easy path of upgrade
Sorry its 7.4.0
I have just created a MVC app and confirm that it behaves as expected so as far as I can tell this just effects Angular
Support: Can you provide a fix for this issue?
I have also reproduced this same issue in my application
**ABP Framework version: ** v5.2.1 **UI type: ** Angular **DB provider: ** Entity Framework Core Tiered (MVC) or Identity Server Separated (Angular): no
[11:36:13 DBG] PermissionStore.GetCacheItemAsync: pn:U,pk:396534cd-6df9-2a23-e034-3a030f5495eb,n:AbpIdentity.Users.Impersonation [11:36:13 DBG] Found in the cache: pn:U,pk:396534cd-6df9-2a23-e034-3a030f5495eb,n:AbpIdentity.Users.Impersonation [11:36:13 DBG] PermissionStore.GetCacheItemAsync: pn:R,pk:admin,n:AbpIdentity.Users.Impersonation [11:36:13 DBG] Found in the cache: pn:R,pk:admin,n:AbpIdentity.Users.Impersonation [11:36:13 DBG] PermissionStore.GetCacheItemAsync: pn:C,pk:ePlus_App,n:AbpIdentity.Users.Impersonation [11:36:13 DBG] Found in the cache: pn:C,pk:ePlus_App,n:AbpIdentity.Users.Impersonation [11:36:13 ERR] Grant validation error: Value cannot be null. (Parameter 'value') System.ArgumentNullException: Value cannot be null. (Parameter 'value') at System.Security.Claims.Claim..ctor(String type, String value, String valueType, String issuer, String originalIssuer, ClaimsIdentity subject, String propertyKey, String propertyValue) at System.Security.Claims.Claim..ctor(String type, String value) at Volo.Abp.Account.Web.ExtensionGrantValidators.ImpersonationExtensionGrantValidator.ImpersonateUserAsync(ExtensionGrantValidationContext context, Nullable`1 tenantId, Guid userId) at Volo.Abp.Account.Web.ExtensionGrantValidators.ImpersonationExtensionGrantValidator.ValidateAsync(ExtensionGrantValidationContext context) at IdentityServer4.Validation.ExtensionGrantValidator.ValidateAsync(ValidatedTokenRequest request)
Added context.Services.Configure<AbpClockOptions>(options => { options.Kind = DateTimeKind.Local; });
All seems to be fine now.
