Thank you, but I have already cloned this repo and could not see the angular app. Also, here is my github username sumeyyeKurtulus
Thank you for checking and answering back. For this case, I will need to know about how you have customized the app. You can send a sample project to my e-mail address: sumeyye.kurtulus@volosoft.com
Can you also try redirecting to these pages account/manage and account/security-logs ?
If you do not see any errors in the console, I will need a sample project to be able to help you further.
Hello, I have carefully followed the steps that you have provided in the related support thread. I am suspecting the validity of the necessary tokens. So, the case may be related to the possible errors appearing on the console that will also cause user to be kicked out. Seeing this, I will need to have the log errors.
If the user is able to reach the pages that need authorization, I will need to see the app details to assist you further.
As you kindly pointed out, I was unable to replicate the same issues. I regard the provided GIF as a helpful showcase to demonstrate the situation more clearly.
Hello, I apologize if we were unable to assist you effectively. It seems that we were also not able to fully replicate the issue on our side. To better understand and resolve the problem, it would be extremely helpful if you could provide a sample project through an email (sumeyye.kurtulus@volosoft.com) that clearly demonstrates the issue.
We greatly appreciate your cooperation and thank you for your understanding.
Hello, I have investigated this problem by the following the same pattern. Your problem should have occurred only for
@abp/ng.feature-managementpackage depending on the optional package selection. Also, thank you for reporting the related deprecations. These issues will be resolved by the next release where you can find details here.Hi,
Thanks for looking into this. Good to know there will be a general fix coming but will that also fix the deprecated packages warnings? At least they remained for the solution we did as mentioned above. It seems that a fix for that is already in the /dev branch but for whatever reason never made it into 8.3
Please refund ticket as this is now a confirmed bug.
Thanks.
Sure, I will refund your ticket and the deprecations will also be resolved.
Hello, I have investigated this problem by the following the same pattern. Your problem should have occurred only for @abp/ng.feature-management package depending on the optional package selection. Also, thank you for reporting the related deprecations. These issues will be resolved by the next release where you can find details here.
I wish this could have helped you, but it seems that there’s an aspect of the configuration that I’m not fully knowledgeable about to resolve the issue. From what I understand of your setup, it appears that the problem is not on our side. I understand that the proposed change affects the redirection to the login page in a passive tab after logging off in the active tab, and I apologize for any inconvenience this may cause.
Hello, I believe I had reproduced the same problem. The issue might be related to this condition event.newValue === null as can be seen in the record.
