iOS 8.4 : UIApplicationDelegate in the iPhone App never called reply()

Hi,


I get a "UIApplicationDelegate in the iPhone App never called reply()"-Error when starting my watch-appsince I upgraded my iPhone to iOS 8.4.


With 8.3 everything was fine and working, watch-app starting caused a connect to the phone, there the app came up in background


I found a workaround: If I open my corroponding app on the iPhone and open then my watch-app, it can connect to the iPhone.

It seems to me, that the app doesn't get started any more by the delegate...


No, I didn't change anything else in my project.


Did I miss any changes taken place in iOS8.4 handling this topic?


Anyonee got a clue?


Regards

We are experiencing the same issue with our app. Please see the post I created a few weeks back about this: https://devforums.apple.com/thread/272278?tstart=0. I talked to a developer relations guy at WWDC but nothing has been fixed.


As mentioned in that thread, it seems to only happen to apps that use Main nibs and pass nil as the last argument in UIApplicationMain(argc, argv, nil, nil) in main.m.

Hi,


I experienced exactly the same issue after upgrading my phone to 8.4.


The watchkit app does start the parent app but unfortunately the iPhone app crashes while performing application:handleWatchKitExtensionRequest: . I analyzed the issue and came to the conclusion that iOS 8.4 no longer calls application:didFinishLaunchingWithOptions: before an initial watchkit extension request. Have a look at https://forums.developer.apple.com/message/19850#19850 which details everything.

In my case, we did 3rd party lib initializations in the application:didFinishLaunchingWithOptions: . As a workaround, I extracted the initialization into an extra method. Whenever application:handleWatchKitExtensionRequest: is called, I make sure that the initialization was completed before.


Hope this helps!

I just did some more testing and found I no longer had this issue when building with Xcode 6.4.

Update: I was wrong, using Xcode 6.4 does not solve the issue. My current workaround is to try calling openParentApplication:reply: after a 0.5 second delay and that usually works.

iOS 8.4 : UIApplicationDelegate in the iPhone App never called reply()
 
 
Q