Fabian H.
Fabian H.

Reputation: 133

Google Chrome: DOMException: Registration failed - manifest empty or missing

I am trying to implement Push Notifications on my website (using Pushpad). Therefore I created a "manifest.json" with following content:

{
    "gcm_sender_id": "my_gcm_sender_id",
    "gcm_user_visible_only": true
}

of course I created a valid GCM-Account and have a sender id

I put the manifest.json into my root directory and I also added this line to my index.php:

<link rel="manifest" href="/manifest.json">

Using Firefox everything works fine and I can send and receive push notifications (so I think the manifest-include works fine), but Chrome won't work...

The console shows following error:

Uncaught (in promise) DOMException: Registration failed - manifest empty or missing

I searched Google for a long time and tried everything I found, but nothing works.

What I tried:

  1. created the manifest.json with "Editor" and saved it as type All Types (so no hidden .txt-file) and also with UTF-8-Encoding.
  2. restarted Chrome
  3. cleared Chrome's cache, history, etc.

I really hope somebody can help me.

Upvotes: 11

Views: 14954

Answers (7)

jsbisht
jsbisht

Reputation: 9649

Adding the following block fixed this for me:

self.addEventListener('push', (event) => {
  const title = 'Get Started With Workbox';
  const options = {
    body: event.data.text()
  };
  event.waitUntil(self.registration.showNotification(title, options));
});

Upvotes: 0

Łukasz P
Łukasz P

Reputation: 1

There seem to be three ways to fix this bug: a) No redirects for "manifest.json" file. b) Put a link to this file at the top of the tag. c) Be sure, that there is no other manifest file before this one, cause it seems that web push script will try to import the first one and return an error due to the wrong data. I have tried all three and finally forced Chrome to behave.

Upvotes: 0

Fabian H.
Fabian H.

Reputation: 133

Because I didn't find an answer anywhere out there in the WWW, but managed to get it working after some time I want to provide my solution/answer for other users, who probably have the same problem:

In the file where I inlcuded the Pushpad files I wrote some PHP-Code before the <head>-Tag to include some files, e.g. for database connection. After I moved the PHP-Code below the <head>-Tag everything worked fine.

Upvotes: 0

Rob Frank
Rob Frank

Reputation: 377

This may be an issue with your Service Worker scope. I ran into a similar problem when I rearranged my files/directories. Make sure your sw.js is on the same level as your manifest.json, otherwise the service worker won't be able to find your manifest. Try putting them both in the root of your directory. Optionally, you can specify the scope of your service worker by adding it to serviceWorker.register():

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/sw-test/sw.js', {scope: '/sw-test/'})
  .then(function(reg) {
    // registration worked
    console.log('Registration succeeded. Scope is ' + reg.scope);
  }).catch(function(error) {
    // registration failed
    console.log('Registration failed with ' + error);
  });
}

Read more here: https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers

Upvotes: 1

Shreekanta
Shreekanta

Reputation: 31

I faced same issue,added manifest file right after head tag . which worked for me.Cheers!

Upvotes: 3

Sudhanshu
Sudhanshu

Reputation: 457

For me it was a redirect. The manifest.json must return a 200 status code (must be directly available from the server), without any redirects. You can check the response via

wget --max-redirect=0 https://example.com/manifest.json

or

curl https://example.com/manifest.json

Upvotes: 5

Tom Tang
Tom Tang

Reputation: 1144

Was wondering if your "manifest.json" is public accessible ?

If not maybe you can try to set it public accessible to see if that helps or not.

And it seems that the current chrome, when getting the "manifest.json" won't supply the cookies.

Upvotes: 0

Related Questions