No background sync after restarting browser
I am implementing PWA with a service worker, utilizing Background Sync and IndexedDB in uploading images while user is offline.
So it is working! While offline on uploading an image, nativeFile is pushed to IndexedDB and a unique tag is registered for background sync. After bringing up network to online, the background sync called my function to upload the file from indexedDB to server. That happens when my browser is open.
HOWEVER, in the scenario where uploading while being offline. Then restart the browser and go online, no background sync is triggered after opening it.
Is this how supposed background sync will work? only when browser is open? or am I doing something wrong?
service-worker indexeddb progressive-web-apps background-sync
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
add a comment |
I am implementing PWA with a service worker, utilizing Background Sync and IndexedDB in uploading images while user is offline.
So it is working! While offline on uploading an image, nativeFile is pushed to IndexedDB and a unique tag is registered for background sync. After bringing up network to online, the background sync called my function to upload the file from indexedDB to server. That happens when my browser is open.
HOWEVER, in the scenario where uploading while being offline. Then restart the browser and go online, no background sync is triggered after opening it.
Is this how supposed background sync will work? only when browser is open? or am I doing something wrong?
service-worker indexeddb progressive-web-apps background-sync
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
Background sync should work even if the browser was closed. It was clearly stated in the sample app provided in the documentation. Check these steps to understand more about how the background sync works. After the sending the data (the moment after you hit the send button). You have the option to either close the browser while still be able to send the data.
– MαπμQμαπkγVπ.0
Nov 21 '18 at 10:44
There are some things that can only be done while your app is in foreground, like registering to a sync event for example. Maybe your 'sync' event handler is doing something that is not allowed in background. Can you share your sync handler code?
– rodix
Dec 5 '18 at 3:43
add a comment |
I am implementing PWA with a service worker, utilizing Background Sync and IndexedDB in uploading images while user is offline.
So it is working! While offline on uploading an image, nativeFile is pushed to IndexedDB and a unique tag is registered for background sync. After bringing up network to online, the background sync called my function to upload the file from indexedDB to server. That happens when my browser is open.
HOWEVER, in the scenario where uploading while being offline. Then restart the browser and go online, no background sync is triggered after opening it.
Is this how supposed background sync will work? only when browser is open? or am I doing something wrong?
service-worker indexeddb progressive-web-apps background-sync
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
I am implementing PWA with a service worker, utilizing Background Sync and IndexedDB in uploading images while user is offline.
So it is working! While offline on uploading an image, nativeFile is pushed to IndexedDB and a unique tag is registered for background sync. After bringing up network to online, the background sync called my function to upload the file from indexedDB to server. That happens when my browser is open.
HOWEVER, in the scenario where uploading while being offline. Then restart the browser and go online, no background sync is triggered after opening it.
Is this how supposed background sync will work? only when browser is open? or am I doing something wrong?
service-worker indexeddb progressive-web-apps background-sync
service-worker indexeddb progressive-web-apps background-sync
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
asked Nov 21 '18 at 0:04
Emmanuel Sayson
728
728
Background sync should work even if the browser was closed. It was clearly stated in the sample app provided in the documentation. Check these steps to understand more about how the background sync works. After the sending the data (the moment after you hit the send button). You have the option to either close the browser while still be able to send the data.
– MαπμQμαπkγVπ.0
Nov 21 '18 at 10:44
There are some things that can only be done while your app is in foreground, like registering to a sync event for example. Maybe your 'sync' event handler is doing something that is not allowed in background. Can you share your sync handler code?
– rodix
Dec 5 '18 at 3:43
add a comment |
Background sync should work even if the browser was closed. It was clearly stated in the sample app provided in the documentation. Check these steps to understand more about how the background sync works. After the sending the data (the moment after you hit the send button). You have the option to either close the browser while still be able to send the data.
– MαπμQμαπkγVπ.0
Nov 21 '18 at 10:44
There are some things that can only be done while your app is in foreground, like registering to a sync event for example. Maybe your 'sync' event handler is doing something that is not allowed in background. Can you share your sync handler code?
– rodix
Dec 5 '18 at 3:43
Background sync should work even if the browser was closed. It was clearly stated in the sample app provided in the documentation. Check these steps to understand more about how the background sync works. After the sending the data (the moment after you hit the send button). You have the option to either close the browser while still be able to send the data.
– MαπμQμαπkγVπ.0
Nov 21 '18 at 10:44
Background sync should work even if the browser was closed. It was clearly stated in the sample app provided in the documentation. Check these steps to understand more about how the background sync works. After the sending the data (the moment after you hit the send button). You have the option to either close the browser while still be able to send the data.
– MαπμQμαπkγVπ.0
Nov 21 '18 at 10:44
There are some things that can only be done while your app is in foreground, like registering to a sync event for example. Maybe your 'sync' event handler is doing something that is not allowed in background. Can you share your sync handler code?
– rodix
Dec 5 '18 at 3:43
There are some things that can only be done while your app is in foreground, like registering to a sync event for example. Maybe your 'sync' event handler is doing something that is not allowed in background. Can you share your sync handler code?
– rodix
Dec 5 '18 at 3:43
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403462%2fno-background-sync-after-restarting-browser%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
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403462%2fno-background-sync-after-restarting-browser%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Background sync should work even if the browser was closed. It was clearly stated in the sample app provided in the documentation. Check these steps to understand more about how the background sync works. After the sending the data (the moment after you hit the send button). You have the option to either close the browser while still be able to send the data.
– MαπμQμαπkγVπ.0
Nov 21 '18 at 10:44
There are some things that can only be done while your app is in foreground, like registering to a sync event for example. Maybe your 'sync' event handler is doing something that is not allowed in background. Can you share your sync handler code?
– rodix
Dec 5 '18 at 3:43