-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overlay components cannot find the component to present from #7605
Comments
Debugging notes: cant seem to reproduce this with the latest master |
Added a test for this with this pr: #7606 |
Since this issue was added to the beta.12 milestone, is it safe to bet that a fix won't be released until then? That's totally fine and understandable if that's the case- that's life working with (amazing) beta software. Are there any instructions anywhere on how to properly downgrade back to a previous beta version that would be recommended? |
@TheBrockEllis Good question! We normally do a few nightly releases before doing another full beta release, so the fix for this should be available before beta.12 (its already fixed on the master branch). Also, just so you know the workaround for this is to just wrap your logic that is in your |
Thanks a bunch, @jgw96! I'm working on 3 separate ionic apps right now and use the loading component pretty extensively. I'll move forward and use the setTimeout with the Loading component inside of the |
Thanks for all the kind words! 😃 |
Hmmm, does not seem to be fixed in the latest nightly, will be looking further into this. |
When I set the type to Setting the type to
Makes the Loading component unusable. |
LoadingCtrl = handles creating loading views let l:Loading = loadingCtrl.create(...);
l.present(); |
Setting the type as Thanks for pointing out that one. @Kobzol |
is there a schedule for fixing the issue? |
Note to team: this seems to be isolated to tabs apps, cant seem to repro with the test i added or a sidemenu app, but can repro with a tabs starter. |
Can anyone point out a hack around this? setTimeout? |
@EralpB the current workaround is to put your |
ngOnInit() { presentLoading(texto: string): Loading { workaround... |
loadingCtrl.create is throwing the following error suddenly
tried various workarounds but can't seem to fix |
Hello all! Thanks for all the info. I am happy to report that this has been fixed and will be in the beta.12 release. Thanks for using Ionic! |
Short description of the problem:
Opening an overlay component in
ionViewDidEnter
never actually presents the component because the overlay cannot find the component that it should present from.This is the NavPortal when opening an overlay component in
ionViewDidEnter
:This is the NavPortal when opening an overlay component in a timeout in
ionViewDidEnter
:Steps to reproduce:
ionViewDidEnter
Which Ionic Version? 2.0.0-beta.11
The text was updated successfully, but these errors were encountered: