Issue with Blazor PWA - progressive-web-apps

I am fairly new to Blazor PWA and I am creating a blazor Progressive Web Application by following this link. I am in need of running my web application as a native mobile app. Therefore, I am publishing my contents in to azure for making it as a secured (https) link. Once I published my contents from bin\Release\{TARGET_FRAMEWORK}\publish\ to azure, I am getting the below error.
Service worker: Install
Failed to find a valid digest in the 'integrity' attribute for resource 'https://domain/index.html' with computed SHA-256 integrity '24cvRtDoUxDkJ3HuCGqYq81Jhyp/VgpUn8C5SrxMGG4='. The resource has been blocked.
Unknown error occurred while trying to verify integrity.
service-worker.js:1 Uncaught (in promise) TypeError: Failed to fetch
On exploring the application tab of browser, it gives me like this.
Also I tried with pwa builder by copying my published app link. It says that it could not find app manifest .

Related

Ionic Appflow deploy failing with api access error

My Appflow deployment to the Playstore keeps failing with this error:
Google Api Error: Invalid request - Access Not Configured. Google Play Developer API has not been used in project before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/androidpublisher.googleapis.com/overview?project=xxxx then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
But the Service Account is enabled and linked to the Play Store account with Release Manager perms, and is even tracking requests when I try to do a build

how to fix ERROR_DESTINATION_NOT_REACHABLE error in azure web app deployment using VSTS

I am using VSTS pipeline to deploy asp.net core 2.2 MVC to azure web app.
The last step which is deploy to azure fails - please see the error below:
##[error]Failed to deploy web package to App Service.
2019-01-08T21:39:47.3810424Z ##[error]Error Code:
ERROR_DESTINATION_NOT_REACHABLE More Information: Could not connect to
the remote computer ("our website url"). On the remote computer, make
sure that Web Deploy is installed and that the required process ("Web
Management Service") is started. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Error: Unable to connect to the remote server Error: A connection
attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because
connected host has failed to respond ????:443
I even tried to Take App Offline but no luck:
However, it works fine if I publish the web app through Visual studio.
The problem was the subscription we were using has a firewall in place. So there was no way to get into firewall by even doing things like adding "WEBSITE_WEBDEPLOY_USE_SCM" = false in the app setting of web service.
The only solution we could think of was to create an agent inside a VM sitting inside the same firewall.
Recreate web app in Azure Portal -> Make sure target framework selected correctly.
I had accidentally set this to docker previously during my web app setup in the portal and this error was produced as well. I was using a MVC .NET 4.7 project and trying to use web deploy.
Hopefully this helps someone who has perhaps set up their web app incorrectly in the azure portal.

Unable to Publish .Net backend Service Project into Mobile App service

I have recently migrated my .NET backend Mobile service to App Service, then I tried to publish the updated Service Project to the App Service but it is failing and getting an error saying
Severity Code Description Project File Line Suppression State
Error Web deployment task failed. (Connected to the remote computer ("******.publish.azurewebsites.windows.net") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.)
I have downloaded the Publish Profile from the portal Mobile app command Get Publish Profile option.
Then I imported it to my service project under publish wizard using Import option, I got two profiles one is FTP another one is Web Deploy I tried both option but no luck.
According to the error message it is saying UNAUTHORIZED so, where can I get/see the user name and password of my Mobile App in Azure Portal?
Thanks,
Narendra Macha.
This is a known issue for which a fix is in progress. You can workaround this by adjusting the publish settings to use the scm endpoint for your site, as captured here.

IdentityServer3 MVC App with Windows Authentication

I'm working on creating an MVC Web application backed by an API which uses IdentityServer3 and is compatible with Windows Authentication, but I'm losing my custom claims in the process.
To this end, I've deployed this project: https://github.com/IdentityServer/IdentityServer3.Samples/tree/master/source/MVC%20Authentication
When I deploy it to IIS7 I cannot access either of two pages which display claims information until I turn on Windows Authentication. When I do this, I have access to the secure Web Page that shows claims and the API that shows claims. This is promising, but these displayed claims are SidGroups, and Default claims, respectively. I lose my custom claims.
Monitoring traffic in Fiddler, I notice that when hitting the protected claims page, there are two failed attempts which 401 followed by the successful attempt but which displays the wrong claims.
Has anyone encountered this? Does any one know the location of a working example of a Windows Auth compatible IdentityServer? I've looked over several tutorials which imply it's possible but I don't think they are compatible with IdentityServer3.

Azure facebook login on localhost

For my cordova application i am running a Azure .net backend.
To access it from the client i use the mobile service client plugin for cordova.
Now to my problem:
I want to allow a facebook login which is already supported by the mobile service client. Therefore i registered a FB-application as described in the azure tutorial
Everything works well when i access the published backend. However if i am running it locally, the facebook login fails without any helpful error message.
It must be a problem with the facebook app settings.
For the case where i am running on localhost, i created a second testapplication with the following settings:
For the valid oAuth redirect URIs i have tried different things.
Does anyone have an idea how i could solve this?fa