![FIrefox - Android logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-37-28-a0d9f0_1.png)
Embedded- / WebView blocks when link should be opened in app
Version 125.2.0, Android 11 Settings: Firefox is default browser. 'Open links in apps' is set to 'Ask before opening'
Scenario:
- With the Swiss payment app 'Twint' I scan a QR-code for a payment
- This will open the embedded browser to show a payment site (sbs.twint.ch)
- After entering the amount and pressing submit, the flow is supposed to return to the Twint-app. However, here it just blocks and I cannot navigate anywhere or return to the app manually
Workaround:
- When the embedded view shows, in its menu, I can select 'Open in Firefox'
- Entering the amount there and pressing submit, the popup shows, asking me whether 'to open the link in app'. When I confirm, I am redirected back to the app and can confirm the payment there.
I suspect, the webview does not show the popup but wait for it to be confirmed and thus the flow is blocked. I have searched the forum but could not find anything matching. Still, is that a known issue?
Version 125.2.0, Android 11
Settings: Firefox is default browser. 'Open links in apps' is set to 'Ask before opening'
Scenario:
* With the Swiss payment app 'Twint' I scan a QR-code for a payment
* This will open the embedded browser to show a payment site (sbs.twint.ch)
* After entering the amount and pressing submit, the flow is supposed to return to the Twint-app. However, here it just blocks and I cannot navigate anywhere or return to the app manually
Workaround:
* When the embedded view shows, in its menu, I can select 'Open in Firefox'
* Entering the amount there and pressing submit, the popup shows, asking me whether 'to open the link in app'. When I confirm, I am redirected back to the app and can confirm the payment there.
I suspect, the webview does not show the popup but wait for it to be confirmed and thus the flow is blocked.
I have searched the forum but could not find anything matching. Still, is that a known issue?