Hi,
I'm developing an independent WatchOS application, and trying to use background URL sessions to download new content for complication update.
I think my download tasks are scheduled up appropriately, during a background refresh, following all documented guidelines from apple documentation.
Everything seems to work as intended on the simulator.
But when running on the real device (from XCode, using a self-signed certificate), the updates become quite unreliable (and the debug process is very frustrating btw).
Most of the times, the scheduled download never finishes until the app returns to foreground.
And I get the following error in the logs :
I read that this might be due to a code signing issue. Does it mean that I have to register to an apple developer account to get it working on the real device ? (Needless to say that I'm not naturally inclined to subscribe while I'm not sure to get the app running as intended...)
Thanks a lot for any help
I'm developing an independent WatchOS application, and trying to use background URL sessions to download new content for complication update.
I think my download tasks are scheduled up appropriately, during a background refresh, following all documented guidelines from apple documentation.
Everything seems to work as intended on the simulator.
But when running on the real device (from XCode, using a self-signed certificate), the updates become quite unreliable (and the debug process is very frustrating btw).
Most of the times, the scheduled download never finishes until the app returns to foreground.
And I get the following error in the logs :
Code Block BackgroundSession <...> connection to background transfer daemon [interrupted | invalidated]
I read that this might be due to a code signing issue. Does it mean that I have to register to an apple developer account to get it working on the real device ? (Needless to say that I'm not naturally inclined to subscribe while I'm not sure to get the app running as intended...)
Thanks a lot for any help