Failed to find a valid digest in the 'integrity' attribute for resource and Not Refresh Automatically in browser load in Blazor WASM - progressive-web-apps

have a Blazor WASM app that I have been working on for a period and it has been working fine up to now. I suddenly started getting this error in Live not in development,
After add the PWA is Error Came. Browser not refresh automatically after implement the PWA.
Detail:
.net 5.0
azure app service
Cache not referesh in initial browser Load.

Related

Failed to register a ServiceWorker for scope "https://crewapp.azurewebsites.net/" in Flutter

Getting this error when I run my app that has been deployed to Azure App Services. with .net core 6 and Windows
I have run my Flutter web app on IIS and on Github Pages it works fine there
Does flutter web has any dependency i.e it required node.js for deployment
This is the error i get in below image

My Ionic 5 app release version not working

I built my an app with Ionic 5, The app is makes requests to an API which I made with Laravel 8, data is sent in json form while an API key is required and it is sent in the headers section.
Everything works fine when the App is built in debug version however the release version does not even give an indication of what's happening. For example the login button when pressed it does not do anything it only gives a timeout message which I had set in the app to let the user know the process failed.
The debug app works perfectly without any issues but the release app does not.
I'm sorry I can't post the entire code here since I can't pinpoint where the error seems to be coming from and it's a lot of code.
App - Ionic 5, Angular.
API - Laravel 8
Requests in JSON
Headers - API Key
I later checked the app logs on Android Studio logcat and this is the error that kept popping up: "E/chromium: [ERROR:ssl_client_socket_impl.cc(981)] handshake failed; returned -1, SSL error code 1, net_error -202"
Make sure that your server start with https and have a valid SSL certificate.

Google playstore app unable to access api endpoints

When I build and run my ionic app, it works well and is able to access the remote endpoints. When I build a release and upload it to google playstore, it's updated well, but when I download and install it, the app is unable to access the endpoints. Everything on the server looks and works fine. What could be the cause of this kind of issue?

How to setup VS Code to debug both blazor app and api project

Setting up a Blazor server app and a seperate web api project. What needs to go in launch settings to enable one to step from the blazor app code into the api code?

OpenID Error while testing asp.net app in My Developer Center

I am testing an application I developed using the .NET Devkit 2.0. In My Developer Center I am trying to run the connection tests in the Testing Your App section of the page. The OAuth test works fine but when I try to test OpenID I am getting an error.
When I click the "Test subscribe to app from Intuit App Center (OpenID)" it brings me to the company connect page, then I select the company, then it brings me to a free trial page of my App.
When I click "authorize" I am getting a 404 Error.
The URL points to: https://myserver.com/Error.aspx?aspxerrorpath=/myapp/OpenIdHandler.aspx
Where myserver is the name of my development server and myapp is the name of my application.
I am able to run the application from Visual Studio without a hitch. It connects and runs as expected but when I try it in the dev center it doesn't work properly.
Are my application settings correct?
Should I be pointing to OpenIdHandler.aspx in this instance?
App settings in the dev center:
App URL: https://myserver/myapp/Default.aspx
Disconnect Landing URL: https://myserver/myapp/Disconnect.aspx
Manage Users URL: https://myserver/myapp/Default.aspx
OpenID URL: https://myserver/myapp/OpenIdHandler.aspx
This is my first run at publishing to the Intuit App Center so any suggestions would be a huge help. I'm not even sure if the settings in the dev center are the problem or not.
Thank you
My firewall was not set up properly so it was not allowing any traffic to hit the desired pages of the site. Seems very curious to me that I was able to go to the default page but no others. Any way, it works now.