ionic-framework: Runtime Error Uncaught (in promise): removeView was not found - fast modal dismissing (lazy loaded)

How to hotfix?

@kleeb @napcat @DatBluBat

1. Change all onWillDismiss handler registrations to use the method onDidDismiss instead.
2. Search for any dismiss() call in your code and replace it by dismiss().catch(() => {});. Since there is only this annoying exception being thrown to a potential exception handler, I don’t see any problem in a catch-all-ignore attempt here. Please correct me if I’m wrong.

@JorgeGRC Please try that and tell me if it helps. I remember that I had a similar problem with modals and lazy loading. It also led to the removeView was not found error, but it haven’t had any in common with the issue above. The root cause of that issue was, that the remote view wasn’t found because the module wasn’t loaded properly at the time of presenting. The issue described here is about dismissing an already dismissed view.

I remember that I was able to solve the lazy-loading and modal presenting issue just by fixing my imports, declarations and entryComponents of the related module bundle configuration. This is, for example, how a modal module config looks like on my side:

@NgModule({
    declarations: [
        WelcomePage
    ],
    imports: [
        IonicPageModule.forChild(WelcomePage)
    ],
    entryComponents: [
        WelcomePage
    ]
})
export class WelcomePageModule {}

I call the modal lazy loaded like that:

let welcomeModal = this._modalCtrl.create("WelcomePage");
welcomeModal.present();

You might be missing the entryComponents or proper forChild call.

Also make sure you’ve added the @IonicPage annotation:

@IonicPage({
    priority: "low"
}) 
@Component({
    selector: 'page-welcome',
    templateUrl: 'welcome.html'
})
export class WelcomePage {
}

I’ve the same issue here

Incredible, this bug is still there from nearly one year.

We can not resolve this issue from client side, this issue must be resolved in ionic framework!

@kyr0 version does work for manual dismissing a modal page but not for double ESCAPE press.

right?

I’m only put return false on last line of callback like:

let alert : Alert = this.alertCtrl.create({
    title : 'xyz',
    message : 'abc def',
    buttons : [
        {
            text : 'Ok',
            handler : () => {
                alert.dismiss();
                return false; // put this on last line of callback
            }
        }
    ]
});

I have a same problem… loader.dismiss(); is double, please check…

I get this bug when I use the IonicPage directive and attempt to go back to previous pages.

Same issue here, reported many times by sentry error reporting in my live app 😦

Still occuring even on the nightly build

I updated to the latest version 3.3.0 and this is also happening in my app.

I have reproduced the bug and I found out this bug also effects:

• popover component
• action sheet component
• picker-component
• alert component

this bug can be fixed in many ways:

• By adding an Escape Key Event delay
• or By handling the promise this.viewCtrl.dissmis(...) in each component by simply having an empty catch
• or By adding a boolean flag aboutToLeave

@brandyscarney I can open a PR for this bug, should I open 1 PR per component or one PR for all component.