WCSession.sendMessage: Open iPhone app or not?

Question

Created Sep ’15

Replies 2

Boosts 0

Views 2.4k

Participants 3

I'm trying to use WCSession.sendMessage Watch -> Phone to have the phone perform some data retrieval and reply immediately. Now, the confusing part of this is that I'm not clear on if the iPhone is supposed to be woken up by this even if it is killed or suspened.

The WCSession.sendMessage documentation states:

"Calling this method from your WatchKit extension while it is active and running wakes up the corresponding iOS app in the background and makes it reachable. Calling this method from your iOS app does not wake up the corresponding WatchKit extension. If you call this method and the counterpart is unreachable (or becomes unreachable before the message is delivered), the

errorHandler

block is executed with an appropriate error. The

errorHandler

block may also be called if the

message

parameter contains non property list data types."

However, the documentation for the corresponding WCSessionDelegate method states:

"Use messages to communicate quickly with the counterpart process. Messages can be sent and received only while both processes are active and running."

These statements seem conflicting, can anyone tell me what the expected behavior is? I'm currently seeing the latter, am hoping to achieve the former.

Thanks!

Boost

Answer 1

Yuehan Song OP

Sep ’15

WCSession.sendMessage will wake up your application on iPhone and then the both processes are active and running. in my case , sending message from watch while my iPhone app is not launing is OK

0

Answer 2

yolp OP

Nov ’21

Is there more information to this topic, for example in the docs? Does the iPhone app really wake up, and in what "state" does it wake up? Is it some kind of background state, or does it appear as the new active iPhone app?

In my testing, the app did not wake up, and I have no idea where to look for solutions.

0