Throwing UserFriendlyException is throwing actual exception rather than being displayed as a dialog #9555

9 Answer(s)

• 

  0

  AI-Bot created 3 months ago

  Support Team ABP Agent

  • In ABP MVC applications, throwing a UserFriendlyException should display a user-friendly dialog instead of the raw exception page. If you are seeing the raw exception after upgrading to .NET 9 or ABP Commercial Pro, it is likely due to a missing or misconfigured exception filter or middleware.

  • Ensure you have the AbpExceptionFilter enabled in your MVC pipeline. In your Startup.cs or module configuration, make sure you have:

    services.AddAbpMvcExceptionHandling();
    

  • Also, check that you are not running in the Development environment, as the Developer Exception Page will override ABP's user-friendly dialog. In production, ABP's exception handling will show the dialog.

  • If you have custom error handling middleware or filters, ensure they do not interfere with ABP's exception handling.

  • For more details, see the official documentation:

    • https://docs.abp.io/en/abp/latest/Exception-Handling#user-friendly-exception

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  cstobler created 3 months ago

  I don't see services.AddAbpMvcExceptionHandling(); in my WebModule.cs, so I was looking to add it, but I doesn't seem to be available to add under context.services in the ConfigureServices method. I think I am still missing something here.

  If you need access to my project, it was emailed for a previous ticket: 9542.

  Save Cancel
• 

  0

  alper created 3 months ago

  Support Team Director

  this is development page for errors, try to run it in release mode also environment variable = release

  Save Cancel
• 

  0

  cstobler created 3 months ago

  Would you mind spelling this out for me a bit more? Is this the ASPNETCORE_ENVIRONMENT variable, or another one? I tried experimenting with utilizing app.UseErrorPage() in dev rather than app.UserDeveloperExceptionPage(), and that didn't seem to do anything. It's very possible I am grossly misunderstanding how to go about this, but any advice would be appreciatd.

  Save Cancel
• 

  0

  alper created 3 months ago

  Support Team Director

  there's a condition like this:

  Save Cancel
• 

  0

  cstobler created 4 months ago

  Thanks for pointing that out. I do have that configured, but it is also failing in production as well (this error only arises when I throw a UserFriendlyException shown below):

  Here is my OnApplicationInitialization method:

  

  It is throwing the 500 error when it hits this line:

  I didn't change anything here other than upgrading to Pro, so I think something must have gone awry (which wouldn't be surprising since I had other issues after upgrading). I don't think it should be throwing a 500 error when I throw a UserFriendlyException.

  Save Cancel
• 

  0

  maliming created 4 months ago

  Support Team Fullstack Developer

  hi

  You can add try catch when calling the application service in your razor page. Because your page return type is page(IActionResult) instead of object.

  public virtual async Task<IActionResult> OnPostAsync()
  {
      try
      {
          await AppService....
      }
      catch (UserFriendlyException e)
      {
          Alerts.Danger(L["Your messag"]);
          return Page();
      }
  }
  

  

  Thanks.

  Save Cancel
• 

  0

  cstobler created 4 months ago

  Ok, it seems like maybe in the past when I was getting the user friendly exception dialog, it was because I was using an AJAX request. Using try-catch in the razor page model should allow me to get close to what I need. Thanks.

  Save Cancel
• 

  0

  maliming created 4 months ago

  Support Team Fullstack Developer

  Great

  Save Cancel