NSURLsession using the iPhone for Watch (OS2)?

Hi,


On WWDC session 711, it said so about the NSURLSession :


"In most circumstances, if the users' watch is nearby their paired iPhone device, then we will actually leverage the Bluetooth connection between them, perform the HTTP loads on the phone itself, and deliver the results back to the watch over Bluetooth.

If the user happens to be out and away from their phone, but with their watch, and the watch is connected to a known Wi-Fi network, then we can actually use that Wi-Fi network directly."


So basically "in most circumstances", the Watch uses it's paired iPhone network over it's own connection, right?


My question is to clarify this case:

"If the watch is nearby the paired iPhone, but the iPhone has WIFI off and so is using 3G/4G ... Will the Watch connects to a 'known Wi-Fi' network by itself, or will it use the 3G/4G connection on the iPhone? Which one will take precedence, the iPhone 3G connection or Watch known WiFi?"


Is the priority list will be:

1. iPhone WiFi, 2. Watch WiFi, 3. iPhone 3G

or?

1. iPhone (no matter WiFi or 3G), 2. Watch WiFi


Thanks a lot for answering 🙂 Best wishes 😉

If the watch is nearby the paired iPhone, but the iPhone has WIFI off and so is using 3G/4G ... Will the Watch connects to a 'known Wi-Fi' network by itself, or will it use the 3G/4G connection on the iPhone?

I was curious about this myself so I asked NSURLSession engineering about it. The current situation is that, if the iPhone is available, the Watch will always ask it to do the transfer.

The usual caveats apply here: this is an implementation detail that may change in the future.

Share and Enjoy

Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"
NSURLsession using the iPhone for Watch (OS2)?
 
 
Q