fetch not firing in service worker in Firefox 64












1














I have a GatsbyJS website and I'm trying to load data using fetch but for some reason, it's not firing/the Promise is not returning in Firefox.



This is my service worker code:



self.addEventListener('install', () => {
console.log('Service worker installing...');
// self.skipWaiting();
});

self.addEventListener('activate', () => {
console.log('Service worker activating...');
// listener.waitUntil(clients.claim());
fetch('https://httpbin.org/get')
.then(async (response) => {
const json = await response.json();
console.log(json);
return json;
})
.catch((err) => {
console.log('Failed to fetch because ', err);
});
});


This is the console output in Chrome:
enter image description here



and the console output in Firefox:
enter image description here



For some reason, Firefox doesn't run then or catch. I would appreciate if someone could help me debug this problem.










share|improve this question






















  • just for further debug, can you put a console.log before the const json = ... line
    – Jaromanda X
    Dec 27 '18 at 20:48










  • I added console.log('response returned'); before const json = ... like you asked, and it didn't print 'response returned'.
    – silverAndroid
    Dec 28 '18 at 1:35










  • Wrap the whole fetch chain in a try catch.
    – Jaromanda X
    Dec 28 '18 at 3:04










  • I tried that but nothing happened, one thing I did notice though is when I put the service workers page next to my website, the service workers page flickered with my local site showing up then instantly disappearing.
    – silverAndroid
    Dec 28 '18 at 16:25
















1














I have a GatsbyJS website and I'm trying to load data using fetch but for some reason, it's not firing/the Promise is not returning in Firefox.



This is my service worker code:



self.addEventListener('install', () => {
console.log('Service worker installing...');
// self.skipWaiting();
});

self.addEventListener('activate', () => {
console.log('Service worker activating...');
// listener.waitUntil(clients.claim());
fetch('https://httpbin.org/get')
.then(async (response) => {
const json = await response.json();
console.log(json);
return json;
})
.catch((err) => {
console.log('Failed to fetch because ', err);
});
});


This is the console output in Chrome:
enter image description here



and the console output in Firefox:
enter image description here



For some reason, Firefox doesn't run then or catch. I would appreciate if someone could help me debug this problem.










share|improve this question






















  • just for further debug, can you put a console.log before the const json = ... line
    – Jaromanda X
    Dec 27 '18 at 20:48










  • I added console.log('response returned'); before const json = ... like you asked, and it didn't print 'response returned'.
    – silverAndroid
    Dec 28 '18 at 1:35










  • Wrap the whole fetch chain in a try catch.
    – Jaromanda X
    Dec 28 '18 at 3:04










  • I tried that but nothing happened, one thing I did notice though is when I put the service workers page next to my website, the service workers page flickered with my local site showing up then instantly disappearing.
    – silverAndroid
    Dec 28 '18 at 16:25














1












1








1







I have a GatsbyJS website and I'm trying to load data using fetch but for some reason, it's not firing/the Promise is not returning in Firefox.



This is my service worker code:



self.addEventListener('install', () => {
console.log('Service worker installing...');
// self.skipWaiting();
});

self.addEventListener('activate', () => {
console.log('Service worker activating...');
// listener.waitUntil(clients.claim());
fetch('https://httpbin.org/get')
.then(async (response) => {
const json = await response.json();
console.log(json);
return json;
})
.catch((err) => {
console.log('Failed to fetch because ', err);
});
});


This is the console output in Chrome:
enter image description here



and the console output in Firefox:
enter image description here



For some reason, Firefox doesn't run then or catch. I would appreciate if someone could help me debug this problem.










share|improve this question













I have a GatsbyJS website and I'm trying to load data using fetch but for some reason, it's not firing/the Promise is not returning in Firefox.



This is my service worker code:



self.addEventListener('install', () => {
console.log('Service worker installing...');
// self.skipWaiting();
});

self.addEventListener('activate', () => {
console.log('Service worker activating...');
// listener.waitUntil(clients.claim());
fetch('https://httpbin.org/get')
.then(async (response) => {
const json = await response.json();
console.log(json);
return json;
})
.catch((err) => {
console.log('Failed to fetch because ', err);
});
});


This is the console output in Chrome:
enter image description here



and the console output in Firefox:
enter image description here



For some reason, Firefox doesn't run then or catch. I would appreciate if someone could help me debug this problem.







javascript firefox service-worker






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 27 '18 at 20:15









silverAndroid

431620




431620












  • just for further debug, can you put a console.log before the const json = ... line
    – Jaromanda X
    Dec 27 '18 at 20:48










  • I added console.log('response returned'); before const json = ... like you asked, and it didn't print 'response returned'.
    – silverAndroid
    Dec 28 '18 at 1:35










  • Wrap the whole fetch chain in a try catch.
    – Jaromanda X
    Dec 28 '18 at 3:04










  • I tried that but nothing happened, one thing I did notice though is when I put the service workers page next to my website, the service workers page flickered with my local site showing up then instantly disappearing.
    – silverAndroid
    Dec 28 '18 at 16:25


















  • just for further debug, can you put a console.log before the const json = ... line
    – Jaromanda X
    Dec 27 '18 at 20:48










  • I added console.log('response returned'); before const json = ... like you asked, and it didn't print 'response returned'.
    – silverAndroid
    Dec 28 '18 at 1:35










  • Wrap the whole fetch chain in a try catch.
    – Jaromanda X
    Dec 28 '18 at 3:04










  • I tried that but nothing happened, one thing I did notice though is when I put the service workers page next to my website, the service workers page flickered with my local site showing up then instantly disappearing.
    – silverAndroid
    Dec 28 '18 at 16:25
















just for further debug, can you put a console.log before the const json = ... line
– Jaromanda X
Dec 27 '18 at 20:48




just for further debug, can you put a console.log before the const json = ... line
– Jaromanda X
Dec 27 '18 at 20:48












I added console.log('response returned'); before const json = ... like you asked, and it didn't print 'response returned'.
– silverAndroid
Dec 28 '18 at 1:35




I added console.log('response returned'); before const json = ... like you asked, and it didn't print 'response returned'.
– silverAndroid
Dec 28 '18 at 1:35












Wrap the whole fetch chain in a try catch.
– Jaromanda X
Dec 28 '18 at 3:04




Wrap the whole fetch chain in a try catch.
– Jaromanda X
Dec 28 '18 at 3:04












I tried that but nothing happened, one thing I did notice though is when I put the service workers page next to my website, the service workers page flickered with my local site showing up then instantly disappearing.
– silverAndroid
Dec 28 '18 at 16:25




I tried that but nothing happened, one thing I did notice though is when I put the service workers page next to my website, the service workers page flickered with my local site showing up then instantly disappearing.
– silverAndroid
Dec 28 '18 at 16:25












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53950387%2ffetch-not-firing-in-service-worker-in-firefox-64%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53950387%2ffetch-not-firing-in-service-worker-in-firefox-64%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas