Hello again,
Thank you for the update. I am happy to hear if this has solved your problem. Is there anything I could assist you further on this matter?
Hello again,
Thank you for providing extra details about your problem. We will be looking into this issue for the next patch release. Until we publish a solution, could you try this approach to eliminate the error temporarily?
// app.component.ts
export class AppComponent implements OnInit {
private userMenu = inject(UserMenuService);
private configState = inject(ConfigStateService);
protected session = inject(SessionStateService);
protected windowService = inject(AbpWindowService);
protected readonly localStorageService = inject(AbpLocalStorageService);
ngOnInit(): void {
const tenant = this.session.getTenant().id || null;
this.configState.getOne$('currentUser').subscribe(currentUser => {
if (currentUser?.isAuthenticated) {
// One-time reload when user is authenticated and has tenant
if (tenant && !this.localStorageService.getItem('reloadForTenant')) {
this.localStorageService.setItem('reloadForTenant', 'true');
this.windowService.reloadPage();
}
[
eUserMenuItems.LinkedAccounts,
eUserMenuItems.AuthorityDelegation,
eUserMenuItems.ExternalLogins,
eUserMenuItems.SecurityLogs,
eUserMenuItems.Sessions,
].forEach(item => this.userMenu.removeItem(item));
} else {
this.localStorageService.removeItem('reloadForTenant');
}
});
}
}
Thank you for your cooperation.
I have investigated the reason. However, I cannot produce the same problem on the latest studio version that is 1.1.2.
I suspect that create-lib command would have failed somehow. You could try on this studio version. You can also check your studio ui logs that is under ~/.abp/studio/ui or %UserProfile%\.abp\studio\ui depending on your operating system

Thank you for sharing a project. I have seen that the related library is missing that will correspond to the order service. I am not sure whether it failed to be generated while creating a service on studio, however you can generate the related library using this command
npx ng g @abp/ng.schematics:create-lib
The name should be ordering-service
You should say No for Is secondary entrypoint?
You can let me know if you need further assistance. Thank you for your cooperation.
I see, could you try sending via google drive or any other cloud provider you prefer?
Thank you for providing extra details about your problem. However, I still cannot produce it on my end.
Could you share a minimal reproducible example, so that I could assist you further? Here is my e-mail address: sumeyye.kurtulus@volosoft.com
Hello again, Thank you for your response. I am glad to hear that the version 9.2 is worked on your side.
Thank you, the version 9.2 fixed my problem, another issue comes in, why do I get the layout without side menu on our modules (e.g Home page).
I have also tried to add a component by following the details you have provided. Here is how it looks on the home route for example:
Could you tell me whether you see any error log on the console?
Hello
I noticed a small syntax issue in your code—there is a missing comma between the dependencies:
"ngx-spinner": "^19.0.0",
"ngx-time-mask": "^1.0.1" // Missing comma here
"rxjs": "^7.8.2",
Aside from that, I wasn’t able to reproduce the problem on my end. It would be very helpful if you could provide a minimal reproducible example. You can send it to me directly at sumeyye.kurtulus@volosoft.com.
Additionally, I recommend aligning your Angular package versions to ~19.1.0, as it is the best-supported version for the ABP version you're using.
The sidebar issue is solved, but the user context menu is still not opening when I use a subdomain; if I log in as the host, it's fine. I created a solution from scratch, and I can confirm the behaviour.
Hello again, Thank you for responding and confirming that the sidebar problem does not persist. Also, that would be the best if you could send the solution you created from scratch so that I could help further beforehand. Here is my e-mail address: sumeyye.kurtulus@volosoft.com.
Another option would be to replace the component, but I'm not sure which one is it, I tried eThemeLeptonXComponents.CurrentUser, but seems not to be working.
Yes, this is the correct replacement key, however you would not need such replacement for this case.