Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Navigation property 'Claims' on entity of type 'User' cannot be loaded because the entity is not being tracked.

See original GitHub issue

Abp Version:3.6.2 .Net Core Version:2.1.0 Ef Core Version:2.1

When I upgrade to .net core 2.1, after the user login in, idle for a period of time (without any operation and not close browser), it will throw the following error:

InvalidOperationException: Navigation property 'Claims' on entity of type 'User' cannot be loaded because the entity is not being tracked. Navigation properties can only be loaded for tracked entities.

Issue Analytics

State:
Created 5 years ago
Comments:24 (12 by maintainers)

Top GitHub Comments

9reactions

malimingcommented, Jun 8, 2018

Identity 2.1 made some changes. It re-registered with ISecurityStampValidator

AddSignInManagerDeps

It covers AddAbpSecurityStampValidator<UserSecurityStampValidator>()

So only need to change the registration order can be solved.

 return services.AddAbpIdentity<Tenant, User, Role>()
                .AddAbpTenantManager<TenantManager>()
                .AddAbpUserManager<UserManager>()
                .AddAbpRoleManager<RoleManager>()
                .AddAbpEditionManager<AbpEditionManager>()
                .AddAbpUserStore<UserStore>()
                .AddAbpRoleStore<RoleStore>()
                
                .AddAbpSignInManager<UserSignInManager>()

                .AddAbpUserClaimsPrincipalFactory<UserClaimsPrincipalFactory>()
                .AddAbpSecurityStampValidator<UserSecurityStampValidator>()
                .AddPermissionChecker<UserPermissionChecker>()

                //.AddAbpSignInManager<UserSignInManager>()

                .AddFeatureValueStore<AbpFeatureValueStore<Tenant, User>>()
                .AddDefaultTokenProviders();

1reaction

Greatsampscommented, Jun 7, 2018

Hi,

This is happening for us also after upgrade from 3.5.x to 3.7. We are using Kesteral hosting, so anything to do with IIS recycling can be discounted. (we are still in development only)

What i have found solves the problem is to delete all cookies and restart the browser, at this point you are asked to log in again, and all is well-- clearly not a production solution.

Will update if i learn more about how to reproduce.