Activities of "Sturla"

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.

As you can see here this still isn´t working. I then saw this CLI issue and am wondering if its somehow connected?

Trying to download the GDPR information doesn´t work

• ABP Framework version: v6.0.1
• UI type: Blazor WASM
• DB provider: EF Core
• Identity Server Separated: yes

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);
        }
    }

Hi

We have been trying to update to version 6.0 from 5.3.4 and are having issues getting the login to work for Blazor WASM.

As stated here our CMS is in the IdentiyServer project.

We get a unhandled 400 error like this (only in Azure.. works locally)

We have a ExceptionSubscriber in the IdentiyServer project but we don´t get anything there.

We can log into our MVC public page, no problem.

I just saw the following error message in the console while the Blazor was loading up that could be the cause.

Refused to display in a frame because it se 'X-Frame-Option' to 'sameorigin' What do you think and how should we fix it?

• ABP Framework version: v6.0.0
• UI type: Blazor
• DB provider: EF Core
• Identity Server Separated: yes

And then this article just came out https://community.abp.io/posts/prerendering-blazor-wasm-application-with-abp-6.x-2v8590g3