Activities of "sumeyye.kurtulus"

Since then the mobile navigation bar has a separate replacement key, you will need to customize it by using the NavbarMobile key

    this.replaceComponent.add({
      component: MySettingsComponent,
      key: eThemeLeptonXComponents.NavbarMobile,
    });

This would be enough for this newly added feature. The documentation will be updated accordingly.

Can you try adding this

impersonation: {
    userImpersonation: true,
    tenantImpersonation: true,
},

for your oAuthConfig that is in environment.ts

I’m still encountering issues with running your services correctly. The user availability in the user service is playing a key role in this. Could you check if you are able to retrieve the user as outlined in the provided code?

import { AuthService } from '@abp/ng.core';
import { Component } from '@angular/core';
import { UserProfileService } from '@volo/ngx-lepton-x.core';

@Component({
  selector: 'app-home',
  templateUrl: './home.component.html',
  styleUrls: ['./home.component.scss'],
})
export class HomeComponent {
  get hasLoggedIn(): boolean {
    return this.authService.isAuthenticated;
  }

  constructor(
    private authService: AuthService, 
    private userProfileService: UserProfileService
  ) {
    userProfileService.user$.subscribe(user => {
      console.log('🚀 ~ HomeComponent ~ userProfileService.user$.subscribe ~ user:', user);
    });
  }

  login() {
    this.authService.navigateToLogin();
  }
}

I understand your point now. Could you share your SignalR requests as well?

Hello, this problem should have been solved by this release with this PR.

I am not sure how you are actually handling the packages along with the app, but I am still getting build errors

I get your point, but this should be something not related to these conditions as you may also see from these records with these relative conditions:

1. event.newValue !== null

2. event.newValue === null

3. No condition is provided

The problem persists there in the same way

Hello again,

I completely understand the issue you're facing. However, we're also encountering similar build errors in the project you've provided, which is making it difficult to assist further. As I mentioned earlier, I'll be consulting with my teammates as well. In the meantime, since the problem seems to stem from the frontend, it would be helpful if we could receive a fully working project to investigate further.