[4.0.0-beta.5] Cannot close modal 'overlay does not exist'
See original GitHub issueAfter updating to Ionic 4.0.0-beta.5, I get the following error when calling dismiss()
on a ModalController
when I click on a button:
console.js:35 Error: Uncaught (in promise): overlay does not exist
at resolvePromise (zone.js:814)
at resolvePromise (zone.js:771)
at zone.js:873
at
Closing the modal through the backdrop works normally.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:16
- Comments:21 (6 by maintainers)
Top Results From Across the Web
Error: Uncaught (in promise): overlay does not exist (ionic ...
Scenario: showing loader in ionic modal. Loader needs to be shown before getting data and dismiss it after receiving data. When I debugged...
Read more >Dismiss a LoadingController - Ionic Framework
Hi, I switched to Ionic v4 recently and I have some troubles with LoadingController. I do not succeed to cancel it (when I...
Read more >Modal · Bootstrap v5.2
Modals are built with HTML, CSS, and JavaScript. · Clicking on the modal “backdrop” will automatically close the modal. · Bootstrap only supports...
Read more >body-scroll-lock - npm
... 4.0.0-beta.0, last published: 2 years ago. Start using body-scroll-lock in your project by running `npm i body-scroll-lock`. There are ...
Read more >Changelog - Cypress Documentation
The previously experimental Cypress command, cy.origin() , is now generally available in end-to-end testing. This command allows testing multiple origins in a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bleuscyther if we pass
1
as the last argument, it works only for the first dismissing. We can write something like:it would work. But still looks like bug.
@woodstream Indeed, I have found the same in the case of modal overlays.
This works (within the component launched as a modal):
but this doesn’t:
whereas the latter used to work in the previous version.
I am now using this method as a workaround.