hi
The key point is: If you confirm you have found a valid tenant, then set context.Handled = true; and return a tenant name.
The DomainTenantResolveContributor always breaks the resolve process. It always has a tenant value.
So the second one will not be working anymore.
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.AspNetCore.MultiTenancy/Volo/Abp/AspNetCore/MultiTenancy/DomainTenantResolveContributor.cs#L36
You can add your DomainTenantResolveContributor to change this behavior.
btw you can only call AddDomainTenantResolver once.
Otherwise one of them will not work
What is the angular url?
I need to reproduce the issue.
hi
The below JSON response means the tenant resolves is works. Can you share an online website URL so we can test it online?
We will resolve all nullable warnings in 7.4
in the leptonXtheme , user avatar path 404.
hi
This is fixed in the new version.
You can try only to keep one domain, It works for me.
hi
I will confirm this. : )
hi
PermissionAppService will update the database.
You can check the data in the database and cache. Then check them again after restarting the host X
See what happened to the data change.
