In testing of watchOS 2, GM release, we're finding an intermittent problem where the didAppear method of WKInterfaceController isn't getting called on device. It's pretty random. Maybe 1 in 5 times the method never gets called when the view has appeared. Anyone else seen this?
Same problem here ...
It looks like sometimes "didAppear" and all the methods that should be called after "willActivate" never get called.
In the "willActivate" mehod I set a repeating timer which calls a function that updates the content of an image. Sometimes the timer never fires ...
For me this problem occurs when I turn the screen off and then turn it on very quickly, or sometimes when I launch my app from the glance.
I hope that this will be fixed really quickly, it is a big problem in an app that uses a loop to draw things on the screen.
To me, it's a clear blocker bug. IMO No way can there be a production release until this bug is fixed. It will either break apps completely or make them fail intermittently.
I have investigated this issue because it is influencing my app as well. It appears that no UI updates are being applied when being executed by a GCD timer (dispatch_after) when timer is fired while watch app is asleep (by task switching or dong a palm down). This is a major issue for us and it appeared to get worse with the GM release. I really hope Apple fixes this issue quickly!
same issue here.. my app uses NSTimer with selector, and works perfectly on simulator. but on real device, the timer stops when screen locks and resumes when screen displays. really frustating to see so many bugs in GM release
A related question:
Is the method didAppear supposed to be called when coming into the app by tapping into the App Icon?
What about the didDisappear method? Is it supposed to trigger when the user presses on the Digital Crown to go out of the app?
No — the appearance methods are not called when coming from or going to the home screen.
Very sad to report it, but the didAppear problem wasn't fixed for the production watchOS 2 release. Oh well... I guess the best workaround is simply not to use the didAppear method. Pity.
is that per design or is that a bug ?
This is expected behavior.