Ok I see.
Thanks for having pointed me in the right direction.
I can close this ticket I think.
@ismcagdas ok ; any tip on how to do that the clean way ?
Ok... but we do not use Redis, and we don't plan to enable it just for that bug.
Another suggestion maybe ?
Thanks Simon for this feedback.
From our side it's still not resolved. I don't know if the aspnetzero team has found something.
Maybe your comment will help them to reproduce ?
Hello,
any clue on this ?
We are about to deliver our application to clients next week. We really need this to work as expected...
Maybe this issue is related ? https://support.aspnetzero.com/QA/Questions/9073/Issue-with-retrieving-Permissions-tenant-specific-permissions-from-the-database-for-a-given-tenant
My existing app, the part "i just downloaded it" refers to Firefox, to say that the browser was not corrupted with any cookie / cache stuff
I can add one info : it's definitively related to the bckend (no cookie or local storage problem) :
Hello,
have you received my email ?
Just to inform you, I've just encountered the problem and the application was started 2 minutes before, so it's not a matter of long time etc. I started the application, navigated to it ; I was already logged in as an impersonated tenant user ; immediately "switch back to my account" to the host admin and the permissions for some pages like Tenants were not there. Then I stopped the application in IIS, restarted it, went back to my browser, F5 : the "tenants" menu appeared.
Yes, we use latest ABP packages. I send you our code. We have intensively modified the template project and in order to be able to start it, you would need a lot of third-party / corporate projects, it would be several Go of data. So I send you only the corresponding aspnetzero projects, ask me if you need more.
AspNet Zero v8.8.0 (we first noticed this behavior with the 8.7 version, and maybe before), with Angular. No, long time does'nt seeme to be in account (not sure...). By writing this, I cannot reproduce it. But I encountered that yesterday and my colleagues also noticed the problem on their own environments (with other installations of our applications, and various windows editions).
When it happens :
EDIT : it just happened again. maybe you are finally right : I did not touched the application for several hours (but it was running and the page was open in Chrome).