We managed to figure this out and it was our fault and now everything loads just fine so closing this issue!
So, is this a bug in 6.0.1 and is there a workaround or do we need to wait for next patch?
Thank you, its Sturla@ibeinni.is
Did you see the answer Liangshiwei? https://github.com/abpframework/abp/pull/13772
If I add the .br statement to the web .config file for my abp.io project I just get the error you can see in my answer https://github.com/abpframework/abp/pull/13772#issuecomment-1324630884.
Can you get this to work on your side? I´m VERY apprehensious to get this into next 6.0 patch if there is any change needed on your side.
I asked this question at aspnetcore. Please add more details to it if you feel I´m missing something so we can get the proper help from them to fix this.
Hi, I answered back since I´m not getting this to work, see here.
I've reproduced this problem recently
My issue or Mateworkx's one?
p.s sorry for hijacking your issue Mateworkx
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!
Here we have some extra information in the logs.
Could some CMS file be missing that is causing this error? Note that we have our CMS located in the IdentiService and not the public website.
And btw we have this ExceptionSubscriber
in the IdentiService that only catches this unhandled exception with no details at all.
public class OurExceptionSubscriber : ExceptionSubscriber
{
private readonly ILogger<OurExceptionSubscriber > logger;
public OurExceptionSubscriber (ILogger<OurExceptionSubscriber > logger)
{
this.logger = logger;
}
public async override Task HandleAsync(ExceptionNotificationContext context)
{
logger.LogException(context.Exception);
logger.LogError(context.Exception.StackTrace);
logger.LogError(context.Exception.Source);
logger.LogException(context.Exception.InnerException);
}
}