8 Answer(s)
- 
    0Hi, Lepton theme is not supported for new project but still we maintain our packages. It seems there is problem in the library, Our Angular team will check the problem soon 
- 
    0Hello, thank you for reporting this. It will be fixed by next patch release. So, I am refunding your ticket. 
- 
    0Thank you for your reply. Could you please tell me if there is a temporary fix for this error? Or, if you can specify the release date for the fix, we can arrange the upgrade plan accordingly. 
- 
    0We have the same error with an existing application using the lepton theme. Also, are there any plans to remove the lepton theme so we need to migrate to lepton-x, or is it still OK to use it? 
- 
    0Thank you for your reply. 
 Could you please tell me if there is a temporary fix for this error?
 Or, if you can specify the release date for the fix, we can arrange the upgrade plan accordingly.You can track the latest patch releases for a fix at the following link: ABP Patch Releases. In the meantime, I recommend overriding the function that is causing the issue as a temporary solution. To do this, create a CustomImpersonationServicethat extendsImpersonationService:import { Injectable } from '@angular/core'; import { ImpersonationService } from '@volo/abp.commercial.ng.ui/config'; @Injectable({ providedIn: 'root' }) export class CustomImpersonationService extends ImpersonationService { constructor() { super(); } override isImpersonatorVisible(): boolean { const { currentUser: { impersonatorUserId: userId } = {} } = this.configState.getAll(); return !!userId; } }Once created, add it to the providersarray inapp.module.ts.{ provide: ImpersonationService, useClass: CustomImpersonationService },Let me know if you need further assistance. 
- 
    0We have the same error with an existing application using the lepton theme. Also, are there any plans to remove the lepton theme so we need to migrate to lepton-x, or is it still OK to use it? Hello, the Lepton theme remains valid for use, and there are currently no plans to discontinue its support. 
- 
    0
- 
    0After using the temporary solution, there is no error output. It's great to hear that the temporary solution has resolved the initial issue. But I found this issue Regarding the multiple log outputs in isImpersonatorVisible(), this behavior is expected. The function is likely being called multiple times because it is used in the component's template, which triggers change detection cycles. Angular re-evaluates the function whenever a change occurs in the component, ensuring that the UI reflects the latest state.


 
                                