Activities of "sumeyye.kurtulus"

Thank you for sharing those additional details. I understand that this issue is blocking your progress.

You can continue using the "inject": false setting, especially since Safari is having trouble loading the stylesheet directly. As a final suggestion, you may consider preloading the styles in index.html as shown below:

<link rel="preload" href="layout-bundle.css" as="style" onload="this.rel='stylesheet'" />
<noscript>
  <link rel="stylesheet" href="layout-bundle.css" />
</noscript>

Please let us know if you need any further assistance. Thank you for your cooperation.

I am delighted to hear that your problem has been solved.

Hello, sorry for the delayed response. If you are still experiencing the issue, I recommend overriding the authentication guard as a temporary solution until we release an official fix:

// new-auth-flow-guard.ts
import { AuthService } from '@abp/ng.core';
import { inject } from '@angular/core';

export const newAuthenticationFlowGuard = () => {
  const authService = inject(AuthService);

  if (authService?.isInternalAuth) {
    return true;
  }

  authService.navigateToLogin();
  return false;
};

Then, update your app-routing.module.ts as follows:

import { newAuthenticationFlowGuard } from './new-auth-flow-guard';

{
  path: 'account',
  loadChildren: () =>
    import('@volo/abp.ng.account/public').then(m => m.AccountPublicModule.forLazy()),
  canActivate: [newAuthenticationFlowGuard],
}

Thank you for your continued effort and patience — I understand you've already tried several approaches.

We’ve tried reproducing the issue on both development and production builds, but unfortunately haven’t been able to replicate it so far. Because of that, we’re unable to provide a guaranteed fix at this point.

That said, based on your description, this doesn’t appear to be directly related to Angular’s routing. It’s more likely caused by a deployment or infrastructure-level behavior. Could you please check the following:

• Are there any redirects or rewrites (e.g. in NGINX, Apache, or a CDN) that might be preserving or appending query strings?
• Is there a proxy or load balancer in place that could be modifying request URLs or injecting ?&& patterns?
• Could there be any old links or external redirects pointing to your app with malformed URLs?

If possible, setting up URL rewrites to strip or sanitize these query strings (e.g. redirecting to a clean / path) might help resolve the issue.

We noticed that the request to layout-bundle.css is returning a response with Content-Type: text/html instead of text/css. This usually means the file isn’t found, and the server is falling back to the default page (e.g., index.html).

Could you please check whether anything in your deployment setup might be redirecting unknown paths (like layout-bundle.css) to the Angular app's entry point?

Yes, the order of your providers may lead to circular dependency issues like the one you're encountering.

To help you better, could you please share how you've configured your providers and any related modules? That way, I can take a closer look and suggest a more targeted fix.

Also, have you had a chance to check the sample project here? It might offer some insights or a working reference:https://drive.google.com/file/d/1mZN3B14JMsPf-WH_nQIpRVFgnxOvA46B/view?usp=drive_link

I have also tried on a mobile device. My device is android and I used my default browser for testing.

Thank you for following up, and I am sorry to hear the issue is still persisting.

Since this behavior doesn’t occur in development, it’s likely related to how the application is built or served in production — potentially during the deployment phase. That could be why the query string isn’t being cleaned up as expected.

In the meantime, here's a quick way to programmatically remove any unwanted query like ?&& from the URL once the app loads:

export class AppComponent implements OnInit {
  private router = inject(Router);

  ngOnInit() {
    const rawQuery = window.location.search;
    const isGarbageQuery = rawQuery && rawQuery.match(/^(\?&+)+$/);

    if (isGarbageQuery) {
      const url = this.router.url.split('?')[0];
      this.router.navigateByUrl(url, { replaceUrl: true });
    }
  }
}

This ensures the URL is cleaned without reloading the page.

Let me know if you would need further assistance on that. Thank you for your cooperation.

Thank you for providing extra details, however I cannot produce the same problem on my end.

Hello,

Thank you for the details. The peer dependency warnings occur because some libraries (like @ng-bootstrap/ng-bootstrap and angularx-qrcode) declare compatibility with older Angular versions, while your project uses Angular ~19.1.0.

These warnings are expected and will be resolved in an upcoming patch where you can check from https://github.com/abpframework/abp/releases

A refund for your ticket is being processed — thanks for your cooperation.