transferFile never worked for me, which is why I switched to sendMessage. I cannot find a single example of transferFile on the net where it actually works.
Also, by making us use transferFile, you're making us write so much extra code to handle deleting unused images when they're no longer needed, and there's no information on how to move (or where to move) a file to once it's transferred. You just say to move it out of ~Documents/Inbox/. To where?! The documentation provides a link to a generic topic on file management on OS X, which is less than helpful.
If you can provide a working example of code that shows me how to move a file I've just received, then that might help. Bear in mind, though, that I cannot get didReceiveFile: to actually trigger in the Watch app.
My app (When's That) allows you to choose a picture for your background, and that's the image I want to send to the Watch app, but obviously I don't need to send the full-size image, so I resize it, and want to send the resulting, smaller image.
I don't want to keep the smaller copy of the image on the phone, as that's just a waste of space, and I'd have to handle creating the smaller image when the larger one is chosen, and deleting both the larger and smaller ones when they're no longer referenced.
I thought about using sendMessageData, but that only lets me send NSData, and doesn't include any way of telling the Watch app that this new bit of data it's receiving is for a specific item, i.e. there's no extra metadata I can send to say this is the image for event X.
I cannot include the images as data in the application context, as the payload is too large.
There must be some easy way of sending data across. You say sendMessage is intended for small messages, but allow us to send NSData. What does Apple consider "small"? Is 188kb really that large?
Thanks.