5

I have an iOS app and I programmed a extension for it on appleWatch. I'm sending data (NSDictionary) to the appleWatch extension using transferUserInfo method. Everything works in the simulator but when I'm trying to run the application on real devices, it seems that the iWatch is not receiving anything though the iPhone is sending the data (I found this cause I debugged the sender side).

I have configured the WCSession on both sides. I have conformed the WCSessionDelegate in the class where I'm supposed to receive the data. I'm using session:didReceiveUserInfo: method to receive the data in ExtensionDelegate but still like I said everything works fine in the simulator but nothing is being transferred on real devices.

Does anyone has a clue to what the problem is?

here's the code: in the sender side:

inside my class MensaViewController.m

- (void)viewDidLoad
   if ([WCSession isSupported]) {
        session = [WCSession defaultSession];
        session.delegate = self;
        [session activateSession];
   }
   NSLog(@"A dish is being sent");
  [session transferUserInfo:dishDictionary];
}

dishDictionary is declared inside viewDidLoad method and it contains data.

on the receiver side (Watch Extension) I configure the WCSession and receive data in ExtensionDelegate.m like this:

- (void)applicationDidBecomeActive {
    if ([WCSession isSupported]) {
        session = [WCSession defaultSession];
        session.delegate = self;
        [session activateSession];
        NSLog(@"Session activated in iWatch");
    }
}

and I have this method to receive the data:

- (void)session:session didReceiveUserInfo:(NSDictionary<NSString *,id> *)userInfo{

    NSLog(@"Received data from the iPhone");

    NSArray<NSString*> *dictionaryKeys = userInfo.allKeys;
    for(int i = 0; i < dictionaryKeys.count; i++){
        Boolean equalsMensaString = [dictionaryKeys[i] isEqualToString:@"beilagen"];
        if(equalsMensaString)
            [self handleTransferredDish:userInfo];

        Boolean equalsNewsString = [dictionaryKeys[i] isEqualToString:@"article"];
        if(equalsNewsString)
            [self handleTransferredNews:userInfo];

        Boolean equalsEventString = [dictionaryKeys[i] isEqualToString:@"description"];
        if(equalsEventString)
            [self handleTransferredEvents:userInfo];

    }
}
cronoklee
  • 6,482
  • 9
  • 52
  • 80
Rudy.kh
  • 86
  • 1
  • 3
  • Do you see the `Received data from the iPhone`message in your log. I would recommend you to use `- session:didFinishUserInfoTransfer:error:` to log out the error. By the way, try to put the extension code in the `applicationDidFinishLaunching` method – NeilNie Feb 08 '16 at 17:11
  • Do you receive data on your watch when both sides of the app are open? – Hugo Alonso Feb 08 '16 at 18:27
  • I'm receiving the data in the simulator but when it comes to execute on a real iWatch, I don't get any data to show, not even in the log that I received the data. – Rudy.kh Feb 09 '16 at 15:53
  • I'll try the other method and apply your suggestion and hope that it will work :) – Rudy.kh Feb 09 '16 at 15:54
  • I tried the methods stated here but unfortunately it still didn't work. I found another project and I executed it on the iWatch and it worked perfectly using sendMessage and transferUserInfo. I'll try more and once I figure out what is wrong, I'll post here. – Rudy.kh Feb 09 '16 at 18:47

2 Answers2

2

If you take a look at sources function description, you can see the description of the method you are using for transferring data:

public func transferUserInfo(userInfo: [String : AnyObject]) -> WCSessionUserInfoTransfer

The system will enqueue the user info dictionary and transfer it to the counterpart app at an opportune time. The transfer of user info will continue after the sending app has exited. The counterpart app will receive a delegate callback on next launch if the file has successfully arrived. The userInfo dictionary can only accept the property list types.

So..There's no guarantee that the system will send this userInfo while you are actually using the App.

Use the following method instead:

public func sendMessage(message: [String : AnyObject], replyHandler: (([String : AnyObject]) -> Void)?, errorHandler: ((NSError) -> Void)?)

Clients can use this method to send messages to the counterpart app. Clients wishing to receive a reply to a particular message should pass in a replyHandler block. If the message cannot be sent or if the reply could not be received, the errorHandler block will be invoked with an error. If both a replyHandler and an errorHandler are specified, then exactly one of them will be invoked. Messages can only be sent while the sending app is running. If the sending app exits before the message is dispatched the send will fail. If the counterpart app is not running the counterpart app will be launched upon receiving the message (iOS counterpart app only). The message dictionary can only accept the property list types.

and for receiving:

func session(session: WCSession, didReceiveMessage message: [String : AnyObject], replyHandler: ([String : AnyObject]) -> Void)

Notice That: This send can fail if the counterpart app is not open or the Session is not paired and active. So, in the case you can not miss any data you should use updateApplicationContext or transferUserInfo (I actually prefer updateApplicationContext)

session.sendMessage(messageData, replyHandler: { (replyData) -> Void in
            replyHandler?(replyData)
            }, errorHandler: { (error) -> Void in
                print("error: code:\(error.code) - \(error.localizedDescription)")
                errorHandler?(error)
                 do {
                        try session.updateApplicationContext(messageData)
                    } catch {
                        print("There was an error trying to update watchkit app on the background")
                    }
        })

And make sure you receive this cases with proper implementation of

func session(session: WCSession, didReceiveApplicationContext applicationContext: [String : AnyObject])

Hugo Alonso
  • 6,684
  • 2
  • 34
  • 65
  • I know that, but the problem is, I don't want the user to open his iPhone App each time he wants to check something that is already offered in iWatch App. That doesn't make a sense. Using session:transferUserInfo: I was able to get the data transferred this morning, but after it worked once, it has never worked again. The weird thing about it is that I didn't change not even a single character in my code. It just worked and never worked again even after I restart my mac, the iPhone and the iWatch. – Rudy.kh Feb 10 '16 at 12:34
1

I know I'm too late to answer my own question. We were using Apple Watch 2 and IPhone 5 or 6 (don't remember after 2 years!), what happened was magical as everything started to work as the batterie of the apple watch was really low (in 5-10% range). We didn't have any problem even after charging the apple watch. End!

Rudy.kh
  • 86
  • 1
  • 3