search

madskristensen / WebEssentials.AspNetCore.ServiceWorker

Other
342 stars 61 forks source link

Installability #67

Open cissemy opened 4 years ago

cissemy commented 4 years ago

Hi I am the message : No matching service worker detected.You may need to reload the page , or check that the service worker for the current page also controls the start URL from the manifest. Thanks

JudahGabriel commented 4 years ago

Manifest.json should have a scope '/', and a start_url '/'.

Also, verify there are no errors in the console. If there are errors, particularly around service worker, that may be preventing the app from being installed.

All else fails, post your URL here and we can have a look.

cissemy commented 4 years ago

Hi, This my manifest : { "name": "E-Address", "short_name": "E-Address", "description": "Address Electronique", "icons": [ { "src": "/images/icon192x192.png", "sizes": "192x192" }, { "src": "/images/icon512x512.png", "sizes": "512x512" } ], "display": "standalone", "start_url": "/" } it has : start_url '/'.

On Wed, Oct 23, 2019 at 2:21 PM Judah Gabriel Himango < notifications@github.com> wrote:

Manifest.json should have a scope '/', and a start_url '/'.

Also, verify there are no errors in the console. If there are errors, particularly around service worker, that may be preventing the app from being installed.

All else fails, post your URL here and we can have a look.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/madskristensen/WebEssentials.AspNetCore.ServiceWorker/issues/67?email_source=notifications&email_token=AAAVJCJZINWZ5UWBR36YZIDQQCI3HA5CNFSM4I5FMY42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCMVYQ#issuecomment-545573602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAVJCN3A2WQK4KWZFNWMXTQQCI3HANCNFSM4I5FMY4Q .

-- CISSE M. Y. Sofware/Web Developer Phone :(347) 443-9028

Kuroiyatsu commented 4 years ago

I have the same issue. Using a .net core 3 application.

tarslan commented 4 years ago

I just updated my app to 3.1 I am having the same issue.

interogativ commented 3 years ago

Make sure that when you check the "application" settings in your browser's debug that it is using the "manifest.webmanifest" file and NOT the manifest.json file. I had this problem because I had a reference to manifest.json in my _layout file. Here's the BAD line in my layout file: <link rel="manifest" href="~/favicon/manifest.json"> which has since been removed.