Failure_during_transfer

ArtaudAntonin / Jiri Richter over 8 years ago

Surprised that the thread for this issue doesn't exist yet.

Somewhere in the communication between watch and phone, the comm can sometimes be broken for an unknown reason and IQMessageStatus FAILURE_DURING_TRANSFER will occur.

From my experience, this only happens when both sides (watch and phone) are sending and receiving, and will always break the communication in one way: from phone to watch.
While phone>watch is receiving FAILURE_DURING_TRANSFER, watch>phone is sending messages happily.

This never happens when the comm is only one-way.

Did anyone encounter this issue? Is there any workaround or pointers?

Former Member over 8 years ago

I experienced this but in another direction with an Android phones: if I send data from watch and reply immediately in the onMessageReceived callback, then messages stop to be delivered until bluetooth is disconnected (I put phone in airplane mode for this). Problem doesn't seem to occur if I send reply not within callback but after a short while (I use Handler with weak reference to application/service method, which is invoked after a 500ms delay). Still didn't have enough time to do a complete research, but this scenario seems to be the most stable one so far.

ArtaudAntonin / Jiri Richter over 8 years ago

Thanks for your reply. I have it set up in a similar way - I never answer to a message immediately, on watch nor phone, there is at least 1s delay.
Also setting the phone to airplane mode did not seem to help - once I reconnected, the failures occured instantly. What most puzzles me that from watch the messages flow uninterrupted even though the other way is totally blocked.

Do you have any more thoughts to share?

Former Member over 7 years ago

ArtaudAntonin, i'm running into the exact same problem. Did you ever figure out what was causing this?

Alexis_Lecanu over 7 years ago

Same problem, Do you have a solution ?

Former Member over 7 years ago

Hey folks,

Still trying to get this one bumped. I know it's holding some of you up so I'm trying to communicate that as clearly as I can.

Thanks,
- Coleman

ArtaudAntonin / Jiri Richter over 7 years ago

Thanks a lot Coleman. Can we help in any way?

I have just found out that the issue is truly just in the Communication API. When I start getting the FAILURE_DURING_TRANSFER, I can still send for example connectIQ.openApplication() and get a proper callback response. So some communication still occurs. Just not through theconnectIQ.sendMessage()

Also please note the other thread, where Jonesy found out that restarting GCM seems to workaround the issue - I just confirmed that it works for me as well.