Activities of "sumeyye.kurtulus"

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.

Hi again! Thanks for providing the additional details.

From the error trace, it looks like there’s a configuration issue causing the layoutStyles is not iterable error. To resolve this, please try the following steps:

1. Update your provider configuration: Ensure you're passing the correct layout module to importProvidersFrom by adding either SideMenuLayoutModule.forRoot() or TopMenuLayoutModule.forRoot(), depending on the layout you’re using.

importProvidersFrom(
  SideMenuLayoutModule.forRoot()
  // or
  TopMenuLayoutModule.forRoot()
);

2. Register the theme provider: Add provideAbpThemeShared() to your providers array to properly initialize the shared theme configuration.

providers: [
  provideAbpThemeShared(),
]

3. Safely register the core module:

provideAbpCore(
  withOptions({
   environment,
   registerLocaleFn: registerLocale(),
  })
),

Hello again! Thanks for reaching out and continuing to explore the modular setup.

The issue you're encountering is related to the paths configuration in your tsconfig.json. In recent ABP modular monolith setups, alias resolution—like @proxy—depends entirely on how these paths are configured.

Could you please share the relevant portion of the paths property from your tsconfig.json (or tsconfig.base.json, if you're using a workspace configuration)? This will help us verify if the alias is correctly mapped to the generated proxy folder.

Looking forward to your response—thanks for your continued collaboration!

I couldn’t reproduce the issue on my end. Could you please confirm whether the problem still persists? If so, kindly share additional details such as the ABP version you're using, your operating system, and the browser in question. If possible, you can also share a reproducible example of your project by emailing it to sumeyye.kurtulus@volosoft.com so we can investigate further.

Hello, I understand the issue can be frustrating. I'm still unable to replicate the problem on my side. For reference, I generated the application using the App (layered) template in the latest version of ABP Studio.

In the meantime, I recommend updating the style bundle configuration in your angular.json file as shown below. Ensure the inject property is set to true for proper inclusion during build:

"styles": [
  ...
  {
    "input": "node_modules/@volosoft/ngx-lepton-x/assets/css/side-menu/layout-bundle.css",
    "inject": true,
    "bundleName": "layout-bundle"
  },
  {
    "input": "node_modules/@volosoft/ngx-lepton-x/assets/css/side-menu/layout-bundle.rtl.css",
    "inject": true,
    "bundleName": "layout-bundle.rtl"
  }
  ...
],

Let me know if the issue still occurs after making this change.