jfa-pwa-toolkit | ️ PWA Features to Any Website | Progressive Web Application library

by jfadev JavaScript Version: 0.0.3 License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | jfa-pwa-toolkit Summary

jfa-pwa-toolkit is a JavaScript library typically used in Architecture, Progressive Web Application applications. jfa-pwa-toolkit has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i jfa-pwa-toolkit' or download it from GitHub, npm.

️ PWA Features to Any Website (very Fast & Easy)

Support

Quality

Security

License

Reuse

Support

jfa-pwa-toolkit has a low active ecosystem.

It has 248 star(s) with 30 fork(s). There are 8 watchers for this library.

It had no major release in the last 12 months.

There are 10 open issues and 2 have been closed. On average issues are closed in 56 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jfa-pwa-toolkit is 0.0.3

Quality

jfa-pwa-toolkit has 0 bugs and 0 code smells.

Security

jfa-pwa-toolkit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jfa-pwa-toolkit code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jfa-pwa-toolkit is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jfa-pwa-toolkit releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of jfa-pwa-toolkit

Get all kandi verified functions for this library.

jfa-pwa-toolkit Key Features

No Key Features are available at this moment for jfa-pwa-toolkit.

jfa-pwa-toolkit Examples and Code Snippets

No Code Snippets are available at this moment for jfa-pwa-toolkit.

Community Discussions

Trending Discussions on Progressive Web Application

django pwa error = cannot import name 'url' from 'django.conf.urls

Minimum Chrome version for TWA - options?

Blazor WASM 6.0.0-preview.7.21378.6, Visual Studio 2022 preview 3.1

Dotnet React Template - is it possible to use /index.html

Blazor WASM Project Referencing Error (BLAZORSDK1001)

Unable to hit breakpoints in Blazor WASM

Does a service worker need to cache manifest icons that are not used by the core of the PWA?

How do I change the "Authorising..." message that appears when a Blazor PWA application is being refreshed?

Migrating Chrome USB App API to Web USB API

No Manifest Detected on a PHP Progressive Web Application

QUESTION

django pwa error = cannot import name 'url' from 'django.conf.urls

Asked 2022-Apr-02 at 01:49

Hello I am using Django 4.0.3 and I try to use django-pwa in my project but when i runserver i get the below error.

I followed this tutorial geeksforgeeks:make-pwa-of-a-django-project for including progressive web application feature in my project.

I think url from django.conf.urls is deprecated.

I am sure that must exist some solutions...

Help me please.

Error

...

ANSWER

Answered 2022-Apr-02 at 01:45

django.conf.urls is deprecated in Django 4, so you cannot use django-pwa with your version of Django, you need to use Django 3. Otherwise you could fork/edit django-pwa to replace django.conf.urls.url (that is used in this file) with django.urls.path, see this pull request.

Source https://stackoverflow.com/questions/71713923

QUESTION

Minimum Chrome version for TWA - options?

Asked 2021-Oct-21 at 08:44

I have a Trusted Web Activity app that is displaying a Progressive Web Application by using the Android Browser Helper. The documentation and code indicates that the mobile app only runs properly when the Chrome Browser is 72 or above. The address bar is visible when the Chrome Browser is outdated. I believe I have the option of a Webview-fallback but I prefer not to use Webview as some of the app's functionality is incompatible with Webview.

While testing, when the Chrome Browser is updated on the same device, the trusted web activity runs without any issues.

What options do I have where the address bar isn't visible?

Is the min SDK the only way to set the minimum browser requirements or can I explicitly set a min Chrome Browser version in the Play Console for the app before the user downloads it? (which prompts the user to update the browser before installation)

Thanks in advance!

...

ANSWER

Answered 2021-Oct-21 at 08:44

It's not possible to set a browser version requirement on the Play Console.

Besides falling back to a WebView, or showing the application with the URL bar, the other solution would to block the application from loading and ask the user to update / install a browser that supports Trusted Web Activity.

Source https://stackoverflow.com/questions/69094410

QUESTION

Blazor WASM 6.0.0-preview.7.21378.6, Visual Studio 2022 preview 3.1

Asked 2021-Aug-29 at 11:24

I created a standard Blazor WASM project from the template with individual user accounts, ASP.NET Hosted, and Configured for Https, Progressive Web Application checked.

Running the project, I get this in the Dev Tools:

`crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: Could not load settings from '_configuration/Wtf.Client' createUserManager@https://localhost:44344/_content/Microsoft.AspNetCore.Components.WebAssembly.Authentication/AuthenticationService.js:2:288346

Microsoft.JSInterop.JSException: Could not load settings from '_configuration/Wtf.Client' createUserManager@https://localhost:44344/_content/Microsoft.AspNetCore.Components.WebAssembly.Authentication/AuthenticationService.js:2:288346

at Microsoft.JSInterop.JSRuntime.d__161[[System.Object, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext() in Microsoft.JSInterop.dll:token 0x60000b3+0x156 at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args) in Microsoft.JSInterop.dll:token 0x6000049+0x84 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__27[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000122+0x95 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__26[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000120+0x7d at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__25[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x600011e+0xa7 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService`3.d__17[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000110+0x63 at Microsoft.AspNetCore.Components.Authorization.AuthorizeViewCore.OnParametersSetAsync() in Microsoft.AspNetCore.Components.Authorization.dll:token 0x6000043+0xfd at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task) in Microsoft.AspNetCore.Components.dll:token 0x60000a5+0x7e at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync() in Microsoft.AspNetCore.Components.dll:token 0x60000a3+0x113 at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) in Microsoft.AspNetCore.Components.dll:token 0x6000285+0x65 blazor.webassembly.js:1:30848 Cookie “PHPSESSID” will be soon treated as cross-site cookie against “https://localhost:44344/css/open-iconic/font/fonts/open-iconic.woff” because the scheme does not match. open-iconic.woff crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: Could not load settings from '_configuration/Wtf.Client' createUserManager@https://localhost:44344/_content/Microsoft.AspNetCore.Components.WebAssembly.Authentication/AuthenticationService.js:2:288346

at Microsoft.JSInterop.JSRuntime.d__161[[System.Object, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext() in Microsoft.JSInterop.dll:token 0x60000b3+0x156 at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args) in Microsoft.JSInterop.dll:token 0x6000049+0x84 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__27[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000122+0x95 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__26[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000120+0x7d at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__25[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x600011e+0xa7 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService`3.d__17[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000110+0x63 at Microsoft.AspNetCore.Components.Authorization.AuthorizeViewCore.OnParametersSetAsync() in Microsoft.AspNetCore.Components.Authorization.dll:token 0x6000043+0xfd at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task) in Microsoft.AspNetCore.Components.dll:token 0x60000a5+0x7e at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) in Microsoft.AspNetCore.Components.dll:token 0x6000285+0x65 blazor.webassembly.js:1:30848 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: Could not load settings from '_configuration/Wtf.Client' createUserManager@https://localhost:44344/_content/Microsoft.AspNetCore.Components.WebAssembly.Authentication/AuthenticationService.js:2:288346

at Microsoft.JSInterop.JSRuntime.d__161[[System.Object, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext() in Microsoft.JSInterop.dll:token 0x60000b3+0x156 at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args) in Microsoft.JSInterop.dll:token 0x6000049+0x84 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__27[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000122+0x95 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__26[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000120+0x7d at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__25[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x600011e+0xa7 at Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService3.d__17[[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60],[Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions, Microsoft.AspNetCore.Components.WebAssembly.Authentication, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]].MoveNext() in Microsoft.AspNetCore.Components.WebAssembly.Authentication.dll:token 0x6000110+0x63 at Microsoft.AspNetCore.Components.Authorization.AuthorizeViewCore.OnParametersSetAsync() in Microsoft.AspNetCore.Components.Authorization.dll:token 0x6000043+0xfd at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task) in Microsoft.AspNetCore.Components.dll:token 0x60000a5+0x7e at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync() in Microsoft.AspNetCore.Components.dll:token 0x60000a3+0x113 at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) in Microsoft.AspNetCore.Components.dll:token 0x6000285+0x65

Anyone know what's happening here? I did install "The Essentials" extension by Mads Kristensen, if that matters.

...

ANSWER

Answered 2021-Aug-29 at 11:24

When you create a Hosted Wasm project in VS2020 preview the default start project is set to the Client. That kind-of works for a simple app (no Auth) but it probably is a litle bug.

The simple fix is to right-click on the Server project and select "Set as Startup Project".

Source https://stackoverflow.com/questions/68955870

QUESTION

Dotnet React Template - is it possible to use /index.html

Asked 2021-Jul-18 at 01:44

If I use pure Create React Application (without dotnet), then I can open the react application in two ways (after yarn start):

https://localhost:3000/
https://localhost:3000/index.html

But if I use Dotnet React Template, then there is only one way I can open the application (when I add index.html, I only see the dotnet part of the app, but not react) after dotnet run:

https://localhost:5001/
https://localhost:5001/index.html

I would like to find a way to use index.html here as well.

Why am I asking. I recently tried adding my site as a Bookmark to iPhone's Home Screen.

It turned out that this doesn't just work as a link, but iOS now interprets those sites as Progressive Web Application. That is, additional requirements are imposed on the site. And one of them is having a working index.html.

This is why I would like my Dotnet React application to work properly with /index.html

...

ANSWER

Answered 2021-Jul-17 at 19:32

Go get ClientApp/src/App.js and change the first route to below.

Source https://stackoverflow.com/questions/68423584

QUESTION

Blazor WASM Project Referencing Error (BLAZORSDK1001)

Asked 2021-May-25 at 04:53

I have one Server project and now trying to convert it into Progressive Web Application. When I reference the API, Model, and UI projects to it then the following error comes out:

...

ANSWER

Answered 2021-May-25 at 04:53

"I have one Server project" is a little unclear since we can only see . I assume you want ot convert form a Blazor Server App to a WebAssembly app?

The project type is now WebAssembly but you are including, amongst others,

You can't access a database from a browser app directly. It's not supported and it wouldn't be safe (all clients would have access to the connection string).

This project needs to be split into a Client and a Server (API) part.

Your best course is to create a project (in a temp folder) from the full Blazor Wasm + Asp.Net Hosted + Individual Accounts template. It'll give you a complete reference for what goes where.

Source https://stackoverflow.com/questions/67666574

QUESTION

Unable to hit breakpoints in Blazor WASM

Asked 2021-Apr-23 at 11:43

I am trying to debug a Blazor WebAssembly app but get the following message when trying to set breakpoints:

If I do the action that would hit the breakpoint, visual studio instead opens a new tab that says Unable to retrieve source content (Unable to retrieve source content). I have the same issue in a separate blazor server app, as well as the sample template that is provided when first creating a blazor project (counter.razor and fetchdata.razor).

Here is the info on the app: Target Framework: .NET 5.0 (Current) Authentication Type: None Configure for HTTPS: True ASP.NET Core hosted: False Progressive Web Application: True

I am using Visual Studio 2019 version 16.9.4.

My .csproj file is:

...

ANSWER

Answered 2021-Apr-23 at 11:43

The reason for the error was that my solution path had a "#' in a folder name. This error was discussed https://github.com/dotnet/aspnetcore/issues/22036 which apparently was never resolved if you follow the thread.

Source https://stackoverflow.com/questions/67229121

QUESTION

Does a service worker need to cache manifest icons that are not used by the core of the PWA?

Asked 2021-Apr-13 at 09:42

This question may seem quite essential. However, I could not find an answer in any of the official Progressive Web Application (PWA) documentation.

The manifest.json of my PWA contains quite a bit of icons and even a fairly large screenshot.png that are not essential to the core of the PWA.

...

ANSWER

Answered 2021-Apr-13 at 09:42

The brief answer is "no," none of the (fav)icons or screenshots should be cached by the service-worker.js if the PWA will not use these.

Moreover, manifest.json should only refer to icons targeting the Android and/or Chrome browser. Hence, apple-touch-icon.png should not be mentioned in the manifest.json.

For iOS, it suffices to place the apple-touch-icon.png in the root folder of the scope of your application. The same holds true for favicon.ico.

There are some more rules for Windows and Mac OS X user agents. These can easily be checked by following the guidelines of this favicon generator or by proving your PWA URL to its favicon checker.

For example, it told me that the following line is best best kept out of index.html:

Source https://stackoverflow.com/questions/66971402

QUESTION

How do I change the "Authorising..." message that appears when a Blazor PWA application is being refreshed?

Asked 2021-Feb-22 at 06:46

When an asp net hosted BLAZOR Progressive Web Application is refreshed using browser refresh, PWA application performs an authentication roundtrip. During this time span, main content div displays the text: "Authorising...". Where does this message originate from? My objective is to display a spinner-border along with this message so that the user experience an animation. Here is what I know:

Initial "Loading..." message appears from the index page in wwwroot.
For every AutherizeView, Authorizing section can be used to show custom message.

But I'm unable to locate the source of default "Authorising..." message.

...

ANSWER

Answered 2021-Feb-22 at 06:46

There are two places that need your intention.

First is in your App.razor. The AuthorizeRouteView has a property called Authorizing, where you can add any RenderFragement you want to display during authorizing. Here is the line where the Authorizing... is set.

Source https://stackoverflow.com/questions/66310829

QUESTION

Migrating Chrome USB App API to Web USB API

Asked 2021-Feb-09 at 01:10

I currently have source code for a Chrome App, but as the platform is being deprecated I need to migrate my API to a Progressive Web Application.

As I still want support for USB in my web platform application, it was suggested that I use the Web USB API to retain functionality, but I can't seem to figure out the equivalent's for the following and how to implement them:

...

ANSWER

Answered 2021-Feb-09 at 01:10

The WebUSB API provides a USBDevice interface which is returned by navigator.usb.getDevices() and navigator.usb.requestDevice(). This interface has methods equivalent to all but one of those listed above:

Source https://stackoverflow.com/questions/66110272

QUESTION

No Manifest Detected on a PHP Progressive Web Application

Asked 2021-Feb-06 at 21:24

I'm trying to make my PHP web application into a Progressive Web Application, but when I open Chrome DevTools into the application tab, it tells me there is 'No Manifest Detected' when I have put the manifest.json at the root but my ServiceWorker.js is successfully running.

...

ANSWER

Answered 2021-Feb-06 at 21:24

Move your block directly below the opening tag, so that your is below it. The manifest won't be detected, if there is any output before the document head.

Source https://stackoverflow.com/questions/66072473

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jfa-pwa-toolkit

Create the app icons manually or with the tool PWA Image Generator and replace files in /pwa/icons/. If you have moved the pwa folder somewhere else in your project, edit the PWA_ROOT variable in your /sw.js file. It is important that the file sw.js is in the root of your site. Edit the template of your project to include the metatags and scripts needed as in the following example. Attention with the paths if you decided to move the pwa folder. Edit the manifest file /pwa/manifest.json. You can rename manifest.json to app.webmanifest if you prefer Reccomended by W3C. Attention with the paths of icons if you decided to move the pwa folder. Edit the config file /pwa/config.js. Attention with the paths of icons if you decided to move the pwa folder. At this point your PWA is able to precache static resources, cache the different resources for offline access, icons, splash screen and add to home screen. You may need more features, for this we will use the classes and methods offered by the global variable PWA that will allow us to do things like subscription to push notifications among other things.