WKWatchConnectivityRefreshBackgroundTask never delivered

Originator:dan
Number:rdar://27973107 Date Originated:23-Aug-2016 02:25 PM
Status:open Resolved:
Product:watchOS SDK Product Version:watch OS 3
Classification:Bug Reproducible:
 
When supplying information with any of the the background transfer methods, the watch app seems to be woken, but never forwarded a WKWatchConnectivityRefreshBackgroundTask in Handle. Background transferred data is then lost.

Steps to Reproduce:
1. Following the path defined by the WatchConnectvity sample code
2. Compile, run, and dismiss the Watch app
3. Forward a background message to Watch App
4. See Watch App awoken in background, handle(_:) called, but no WKWatchConnectivityRefreshBackgroundTask is delivered. 

Expected Results:
Expected handle to be passed WKWatchConnectivityRefreshBackgroundTask so we can defer completing the task until after all background information has been processed. 

Actual Results:
App is woken and handle(_:) is invoked, but not passed a WKWatchConnectivityRefreshBackgroundTask, causing the background session to expire immediately, and suspending the app. Background transferred information is then lost. 

Version:
Watch OS 3 beta 6, iOS Beta 6

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!