During all beta versions of Watchkit, I was able to run the watch-watching application without problems, but with the recent release last week (8.2) my willActivate method is almost never called. What happens is awakeWithContext is called, and the clock stands with a spinning spinning twig. Who is this problem with?
I found that locking and unlocking the device (simulator) by entering the -L command will cause the willActivate method to be called. I hope you don’t have to do this on a real Apple Watch.
Just got into the same problem yesterday.
, awakeWithContext, willActivate .
awakeWithContext
willActivate
, ALL awakeWithContext willActivate. awakeWithContext , willActivate .
ALL
awakeWithContext, , .
, , , , , , , . , - , . , " " , . (, ). , ; , 4 , 20 ( ) 4 . - . ; , , , - . ; , , , . , willActivate. , . , awakeFromContext:. , . , .. .. , . - , .