WKRefreshBackgroundTask only handled once per hour
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I've written a Watchkit Extension (WatchOS 5.1.1) where I'm attempting to fetch data every 30 minutes or so.
I've read so far that the background task scheduling is not punctual by the minute, but pretty reliable to use couple times an hour.
I'm scheduling the task using
WKExtension.shared().scheduleBackgroundRefresh(withPreferredDate: Date(timeIntervalSinceNow: interval * 60 ), userInfo: ["time": Logger.getDateString()] as NSDictionary ) { (error: Error?) in
if let error = error {
print("Error occured while scheduling background refresh: (error.localizedDescription)")
}
}
This works, however no matter what Intervall I chose, the task is only executed after around 60 minutes. I've written myself a log where I can see when
func handle(_ backgroundTasks: Set<WKRefreshBackgroundTask>)
is called in the ExtensionDelegate, and I can confirm that the handle is just called not often enough.
My Watch is on >80% batterie so that doesn't seem to be the issue.
Appreciate any input on this!
ios swift watchkit background-process
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
add a comment |
I've written a Watchkit Extension (WatchOS 5.1.1) where I'm attempting to fetch data every 30 minutes or so.
I've read so far that the background task scheduling is not punctual by the minute, but pretty reliable to use couple times an hour.
I'm scheduling the task using
WKExtension.shared().scheduleBackgroundRefresh(withPreferredDate: Date(timeIntervalSinceNow: interval * 60 ), userInfo: ["time": Logger.getDateString()] as NSDictionary ) { (error: Error?) in
if let error = error {
print("Error occured while scheduling background refresh: (error.localizedDescription)")
}
}
This works, however no matter what Intervall I chose, the task is only executed after around 60 minutes. I've written myself a log where I can see when
func handle(_ backgroundTasks: Set<WKRefreshBackgroundTask>)
is called in the ExtensionDelegate, and I can confirm that the handle is just called not often enough.
My Watch is on >80% batterie so that doesn't seem to be the issue.
Appreciate any input on this!
ios swift watchkit background-process
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
WatchOS 5.1.1 seems to have background update problems here. 5.1 was very consistent and was updating continuously, but 5.1.1 has been pretty bad... So if you haven't tried on an earlier version maybe this is related. I've been using it for complication updates for a long time now it it just got super reliable prior to 5.1.1.
– Cobra
Nov 18 '18 at 14:07
Yeah, that actually might explain my issues, I think the behavior was better under 5.1, but wasn't sure. Overall, I'm massively struggeling with the whole topic, did you manage to create an App which does update the complication relaibly for days?
– Axel dabee
Nov 18 '18 at 14:10
add a comment |
I've written a Watchkit Extension (WatchOS 5.1.1) where I'm attempting to fetch data every 30 minutes or so.
I've read so far that the background task scheduling is not punctual by the minute, but pretty reliable to use couple times an hour.
I'm scheduling the task using
WKExtension.shared().scheduleBackgroundRefresh(withPreferredDate: Date(timeIntervalSinceNow: interval * 60 ), userInfo: ["time": Logger.getDateString()] as NSDictionary ) { (error: Error?) in
if let error = error {
print("Error occured while scheduling background refresh: (error.localizedDescription)")
}
}
This works, however no matter what Intervall I chose, the task is only executed after around 60 minutes. I've written myself a log where I can see when
func handle(_ backgroundTasks: Set<WKRefreshBackgroundTask>)
is called in the ExtensionDelegate, and I can confirm that the handle is just called not often enough.
My Watch is on >80% batterie so that doesn't seem to be the issue.
Appreciate any input on this!
ios swift watchkit background-process
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
I've written a Watchkit Extension (WatchOS 5.1.1) where I'm attempting to fetch data every 30 minutes or so.
I've read so far that the background task scheduling is not punctual by the minute, but pretty reliable to use couple times an hour.
I'm scheduling the task using
WKExtension.shared().scheduleBackgroundRefresh(withPreferredDate: Date(timeIntervalSinceNow: interval * 60 ), userInfo: ["time": Logger.getDateString()] as NSDictionary ) { (error: Error?) in
if let error = error {
print("Error occured while scheduling background refresh: (error.localizedDescription)")
}
}
This works, however no matter what Intervall I chose, the task is only executed after around 60 minutes. I've written myself a log where I can see when
func handle(_ backgroundTasks: Set<WKRefreshBackgroundTask>)
is called in the ExtensionDelegate, and I can confirm that the handle is just called not often enough.
My Watch is on >80% batterie so that doesn't seem to be the issue.
Appreciate any input on this!
ios swift watchkit background-process
ios swift watchkit background-process
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
asked Nov 16 '18 at 19:29
Axel dabeeAxel dabee
135
135
WatchOS 5.1.1 seems to have background update problems here. 5.1 was very consistent and was updating continuously, but 5.1.1 has been pretty bad... So if you haven't tried on an earlier version maybe this is related. I've been using it for complication updates for a long time now it it just got super reliable prior to 5.1.1.
– Cobra
Nov 18 '18 at 14:07
Yeah, that actually might explain my issues, I think the behavior was better under 5.1, but wasn't sure. Overall, I'm massively struggeling with the whole topic, did you manage to create an App which does update the complication relaibly for days?
– Axel dabee
Nov 18 '18 at 14:10
add a comment |
WatchOS 5.1.1 seems to have background update problems here. 5.1 was very consistent and was updating continuously, but 5.1.1 has been pretty bad... So if you haven't tried on an earlier version maybe this is related. I've been using it for complication updates for a long time now it it just got super reliable prior to 5.1.1.
– Cobra
Nov 18 '18 at 14:07
Yeah, that actually might explain my issues, I think the behavior was better under 5.1, but wasn't sure. Overall, I'm massively struggeling with the whole topic, did you manage to create an App which does update the complication relaibly for days?
– Axel dabee
Nov 18 '18 at 14:10
WatchOS 5.1.1 seems to have background update problems here. 5.1 was very consistent and was updating continuously, but 5.1.1 has been pretty bad... So if you haven't tried on an earlier version maybe this is related. I've been using it for complication updates for a long time now it it just got super reliable prior to 5.1.1.
– Cobra
Nov 18 '18 at 14:07
WatchOS 5.1.1 seems to have background update problems here. 5.1 was very consistent and was updating continuously, but 5.1.1 has been pretty bad... So if you haven't tried on an earlier version maybe this is related. I've been using it for complication updates for a long time now it it just got super reliable prior to 5.1.1.
– Cobra
Nov 18 '18 at 14:07
Yeah, that actually might explain my issues, I think the behavior was better under 5.1, but wasn't sure. Overall, I'm massively struggeling with the whole topic, did you manage to create an App which does update the complication relaibly for days?
– Axel dabee
Nov 18 '18 at 14:10
Yeah, that actually might explain my issues, I think the behavior was better under 5.1, but wasn't sure. Overall, I'm massively struggeling with the whole topic, did you manage to create an App which does update the complication relaibly for days?
– Axel dabee
Nov 18 '18 at 14:10
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%2f53344223%2fwkrefreshbackgroundtask-only-handled-once-per-hour%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.
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%2f53344223%2fwkrefreshbackgroundtask-only-handled-once-per-hour%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
WatchOS 5.1.1 seems to have background update problems here. 5.1 was very consistent and was updating continuously, but 5.1.1 has been pretty bad... So if you haven't tried on an earlier version maybe this is related. I've been using it for complication updates for a long time now it it just got super reliable prior to 5.1.1.
– Cobra
Nov 18 '18 at 14:07
Yeah, that actually might explain my issues, I think the behavior was better under 5.1, but wasn't sure. Overall, I'm massively struggeling with the whole topic, did you manage to create an App which does update the complication relaibly for days?
– Axel dabee
Nov 18 '18 at 14:10