Watch OS 1.0.1 changed the lifecycle for page-based apps: now willActivate/didActivate get called for the next page to preload it.
I was previously calling updateUserActivity:userInfo:webpageURL: in each of my page's willActivate methods, supplying different userInfo for each page. But now that userInfo gets stepped on by the next page's call to the same method in willActivate.
Any idea how to get around this?
I ended up scheduling a timer for 1 second in the future in
willActivate, then invalidating the timer indidActivate. When the timer fires, it callsupdateUserActivity:userInfo:webpageURL:. I'm not too happy about the arbitrary 1 second interval... I tried 0.5 seconds first, but that was too short (I guess WatchKit is really that slow?).