Wondering if anyone else has seen this? I filed a bug, but now I'm just looking for a workaround.
Here's the set up:
Xcode 7.0 beta 6 (7A192o) running a simple WatchKit 2.0 app
Simulator or real AppleWatch
Swift
1. Create a simple Watch OS 2.0 app
2. Create an initial InterfaceController with 3 controls: 1 WKInterfacePicker and 2 WKButtons
3. Create a second InterfaceController with an identifier of "Next"
4. In awakeWithContext load the picker with 50 strings (e.g. "1" to "50")
5. Make sure picker has an associated action: @IBAction func pickerSelectedItemChanged(value: Int) function (no code is required within function)
6. In first button, call self.myPicker.setSelectedItemIndex(42)
7. In second button, call self.pushControllerWithName("Next", context: nil)
Now, run the watch app and do the following:
1. Tap the button that calls setSelectedItemIndex
2. Then QUICKLY, tap the second button that calls self.pushControllerWithName("Next", context: nil)
Observed result:
When the "Next" InterfaceController loads, it first appears with a small network activity indicator, then loads a large activity indicator, and disables all controls in the "Next" interface controller.