Activities of "sumeyye.kurtulus"

I apologize for the delay in responding. We have reviewed the issue independently of the provided steps and encountered a similar problem. I will be discussing this with my team and will provide an update shortly. Thank you for your patience and cooperation.

Thank you for your inquiry. We would like to inform you that modifications to this component will be available in the next release. We appreciate your continued cooperation.

Hello, you can utilize the component replacement documentation and the key should be eGdprConfigComponents.CookieConsent

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