can you change @volosoft/abp.ng.theme.lepton-x package version as follow

"@volosoft/abp.ng.theme.lepton-x": "~2.4.0"

• delete node_modules
• run yarn; yarn start

can you try this?

hi can you send me your package.json file

hi, can you send us your updated package.json file?

hi TMuska, i believe this documentation below solves your problem;

https://docs.abp.io/en/commercial/7.4/migration-guides/v7_4

Hi, As far as we understand, you suggested a solution to redirect to the login page when the token expires. However, our problem is about being able to continue working without refreshing the page when the token expires. Do you have any suggestions on how we can continue working on the project without redirecting to another page or blocking the operation when the token expires?

• this is wrong, normally when the access_token expires, you get a new generated access_token via refresh_token. the application shouldn't be redirect you to login page again.

• in version 7.1.1 i have created a new application with this command;

  • abp new -t app-pro -u angular
  • and set accesstoken expire date to 5 seconds;

• here is how the token regenerated; this is the normal behavior.

• make sure about your configurations in environment file

Hi, have you tried the check remember me button?

this attribute is excatly what you need in your case

hi, if you remove some of the admin permissions you will lose access to related sections.

for example

• i have removed these permissions and no longer access to actions button in roles page

giving permissions back to admin or resetting the database solves the problem. I have tried again for you and it worked properly on me.

Could you give me more detail, maybe i can help you.

hi @alexander.nikonov, we still cannot produce your case.

could you please tell us the steps of producing the problem in a new project. we would like to help you if we can.

it is enough to update your version in package.json when we released the patch

then run yarn command in terminal

Hi, We have created an pull request about this issue, it will be fixed in 7.4 patch

Thank you for reporting