You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Capacitor 2.x, the Browser plugin should trigger the browserFinished event as the in-app browser is dismissed. On Android it does not. Instead, the app needs to become inactive and then resumed again. Only then does the browserFinished event listeners get called.
Expected Behavior
iOS displays the expected behavior: browserFinished event listeners get called immediately.
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out.
Bug Report
Capacitor Version
Platform(s)
Android (tested on Emulator API 29)
Current Behavior
For Capacitor 2.x, the Browser plugin should trigger the
browserFinished
event as the in-app browser is dismissed. On Android it does not. Instead, the app needs to become inactive and then resumed again. Only then does thebrowserFinished
event listeners get called.Expected Behavior
iOS displays the expected behavior:
browserFinished
event listeners get called immediately.This video expected behavior (iOS) vs. buggy behavior (Android).
Code Reproduction
A small project reproducing this issue can be found at @fohlin/cap-browser-events-repro.
Other Technical Details
npm --version
output: 6.14.8node --version
output: v14.15.0pod --version
output (iOS issues only):Additional Context
Possibly related to: #2332
I realize that development is focus on Capacitor v3, but it would be extremely appreciated if someone has an idea for a fix for this. 🙏
The text was updated successfully, but these errors were encountered: