Anyone seeing Modal issues with 2.0 beta 8?

[iignatov]

@webprofusion

Found the solution for me: … Turns out if I wrap it in a NgZone.run it works now …

I’d say that it’s rather a workaround for a problem existing somewhere in your project:

@iignatov

IMHO this is rather a workaround than a solution because if you need to use NgZone to trigger UI updates from code which is inside the Angular zone (which AFAIK is valid for the code in any Angular component unless the code is executed in an external library) then most probably there’s an underlying problem that’s breaking the Angular’s change detection (which you’ll have to solve sooner or later).

In case that you updated your project from an earlier version of the framework I would suggest to check if you performed the update properly. If you missed something by the update, it might result in such problems. Check out the following post for more details:

Ionic2 load ion-toggle or ion-select at will from promise?

I believe that your problem might be caused by the following line in your app.ts: import 'es6-shim'; You need to remove this - check out the guide for updating to beta.6. I would also recommend you to use Node v4/v5 but not v6 because it’s not supported yet:

However if you’re sure that you updated your project correctly then this behavior might be related to the following problem with Observables and zone.js (which should be fixed by now):

ngFor Not Updating

@finke The code looks OK. I guess that it might be something zone-related, e.g. like the following zone.js issue: Losing zone in RxJS and fetch. I’ll suggest you to check in which zone your code is being executed: onGetNear() { // ... this._dataService.nearbySearch(req).subscribe(res => { this.places = res; console.log(Zone.current.name); console.log(this.places); }); }