FBSOpenApplicationErrorDomain Code = 3

I just added the Watch app to my project and tried:

override func awakeWithContext(context: AnyObject?) { super.awakeWithContext(context) let res = WKInterfaceController.openParentApplication(["key" : "value"]) { (replyInfo, error) -> Void in print("replyInfo : \(replyInfo) + error \(error)") } print(res) // true here } 

In my AppDelegate, I wrote:

 func application(application: UIApplication, handleWatchKitExtensionRequest userInfo: [NSObject : AnyObject]?, reply: ([NSObject : AnyObject]?) -> Void) { reply(["replyKey" : "replyValue"]); } 

When I launch the Watch app, I only have:

replyInfo: [:] + error Optional (error Domain = FBSOpenApplicationErrorDomain Code = 3 "Operation could not be completed. (FBSOpenApplicationErrorDomain eor 3.)")

Screenshot for error message

Is it because of the simulator? Do you know what you are doing wrong?

Thank!

+45
ios ios-simulator watchkit compiler-errors apple-watch
Jul 15 '15 at 19:07
source share
5 answers

iOS Simulator → Reset Content and Settings ...

Worked for me

iOS Simulator → Reset Content and Settings ... → Reset

+97
Sep 29 '15 at 14:39
source share



Save your settings




Reboot Simulator:

  • Click the Simulator app
  • Simulator> Exit Simulator or CMD + Q
  • Click on xcode
  • Project> Run or CMD + R
+28
Nov 11 '15 at 22:25
source share

For those who use real equipment, not a simulator, I had this problem. The problem is that I selected my individual developer account as my signing code. In doing so, I had to go to:

Settings> General> Profiles> Device Management> (my email address)

and then click Trust (my email address) to trust my individual account.

After I did this, cmd-R executed my code perfectly on my watch / phone.

+4
Sep 22 '16 at 17:23
source share

Try to return to the view controller and run it again in the simulator; It worked for me in Xcode 7.2.

+1
Feb 06 '16 at 22:27
source share

I got it while working on a real watch. It turned out that the developer account does not trust the iPhone. Settings-> Device Management → ...

+1
Aug 23 '17 at 21:15
source share



All Articles