ionChange is separate from Angular change detection. Have the ionChange of your ion-select call changeDetectorRef.detectChanges() so Angular knows to update the DOM.
@AaronSterling do you mean like this: <ion-select ... (ionChange)="changeDetectorRef.detectChanges()">?
If so, it seems to be causing my app to fail to load. And I still donāt understand why that would cause Case 1 to fail while Case 2 worksā¦Iām not interacting with the pages in any way, thatās just how they load.
@AaronSterling Iām using Ionic 2.2.0. Iām not getting any error messages, just a blank screen with a loading icon instead of the ionic favicon. Currently Iām working on a mockup, so thereās very little code in the controller. Edit: just noticed a bug in my data mocking that was causing an infinite loop, so the blank screen was unrelated to the (ionChange). Sorry for assuming it was your suggestion!
@rapropos Changing showing to match the value of the selected option worked for the foobar-ified version that I posted, but itās not working in the real deal, where both showing and the selectedvalue are set to { level: 1, published: true }. Edit: Could it be the object thatās messing things up? Using inspect, I see: ng-reflect-model="[object Object]"