Open Closed

Icons Missing From New Blazor WASM Project #3870


User avatar
0
mateworkx@gmail.com created

Support Team,

I've hit several issues with version 6.0.0 and requesting assistance in resolving them. I've added a new Blazor WASM project along with MAUI for mobile. After running the application I'm getting some unexpected results. First of which is that no icons are being displayed. This may be due to the second issue which, probably should be the first issue but... anyway. There appears to be a dependency missing or inaccessible and I'm not sure how to fix this. Please see the screenshots attached. Also, MAUI project is missing styles.xml and such. But I should probably create another ticket for this possible bug.

  • ABP Framework version: v6.0.0
  • UI type: Blazor
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): No
  • Exception message and stack trace: See attached screenshot.
  • Steps to reproduce the issue:" Utilize Abp Suite to create a new Blazor WASM project with MAUI and PWA. No public site etc. Run the application and no icons appear.

6 Answer(s)
  • User Avatar
    0
    EngincanV created
    Support Team .NET Developer

    Hi, can you run the abp bundle command in your Blazor project and then re-run the project?

  • User Avatar
    0
    Sturla created

    Hi, can you run the abp bundle command in your Blazor project and then re-run the project?

    EngincanV we are having his issue here https://support.abp.io/QA/Questions/3868/Issue-logging-into-Blazor-WASM-only-on-Azure-after-updating-to-60-and-migrating-to-opendict

    Could it be we need to run abp bundle in our pipeline? Everything works fine in local development!

  • User Avatar
    0
    EngincanV created
    Support Team .NET Developer

    Could it be we need to run abp bundle in our pipeline?

    No, you don't need to add the abp bundle command into your pipeline. I've reproduced this problem recently (and abp bundle fixed it), I'll try to reproduce it again and write you back.

    In meantime, you can try:

    abp clean
    dotnet build
    abp bundle
    

    these commands in order and try again. (I had this problem on local development and this was solved it)

  • User Avatar
    0
    Sturla created

    I've reproduced this problem recently

    My issue or Mateworkx's one?

    p.s sorry for hijacking your issue Mateworkx

  • User Avatar
    0
    mateworkx@gmail.com created

    @Sturla and @EngincanV,

    Running the abp build command did resolve the issue that I was facing. Thank you for your response and recommended solution.

  • User Avatar
    0
    EngincanV created
    Support Team .NET Developer

    @Sturla and @EngincanV,

    Running the abp build command did resolve the issue that I was facing. Thank you for your response and recommended solution.

    Great to hear that!

Made with ❤️ on ABP v9.1.0-preview. Updated on December 05, 2024, 12:19