You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the viewStore.send(.sendMessage) seems to be working fine.
However,it is not while receiving message.
The message could be received only once, then the rest of the message from companion/counterpart, seems to be neglected.
I would say that I may have done something wrong while binding the received value from delegate, but I have no idea how can I fix it to make it async and fit it to be implemented in client. It would be great I could get any reference, or advice. Thanks ahead.🙏🙏
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Here is my initial effort in creating a WatchConnectivityClient.
Just for a test, I implemented only sendMessage, and didSendMessage.
and here is the example AppReducer:
The example view that is calling the viewStore is implemented as below:
the
viewStore.send(.sendMessage)
seems to be working fine.However,it is not while receiving message.
The message could be received only once, then the rest of the message from companion/counterpart, seems to be neglected.
I would say that I may have done something wrong while binding the received value from delegate, but I have no idea how can I fix it to make it
async
and fit it to be implemented in client. It would be great I could get any reference, or advice. Thanks ahead.🙏🙏Beta Was this translation helpful? Give feedback.
All reactions