-
Notifications
You must be signed in to change notification settings - Fork 586
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
bug(@capacitor/browser): Urls without https cause browser.open to crashes application #2036
Comments
This issue has been labeled as |
Updating the issue to reflect that this issue is about catching the error thrown off from not having a valid URL |
i have same crash log like
|
We are using same @capacitor/browser ^5.2.0 version and having the same issue on adding the app to store. Can we have any update on this issue? the crash report is below,
|
Had similar issue, but with valid links and also I found the cause so I will comment here. I had the exact same stack trace but I was opening a valid link. Turns out the client never had a browser installed. The case was that said customer had 2 profiles -> personal and work. They installed the app on the work profile, had chrome installed on their personal profile but not on their work one. This cases the app to crash as soon as Not sure if this should somehow be handled from capacitors side, but I would at least recommend that it is documented somewhere, as all similar queries are about broken URLs and people might spend hours on this silly issue. |
In my case, I wanted to redirect to a |
Bug Report
Plugin(s)
@capacitor/browser ^5.2.0
Capacitor Version
Platform(s)
Android
Current Behavior
This happens when the app is opened from the push listener 'notificationActionPerformed'
In the notification data: urlToOpen = 'www.google.com'
When using .open({url: urlToOpen}) app crashes & stays unresponsive until app data are cleared
If the urlToOpen = 'https://www.google.com/' --> works as expected.
Expected Behavior
Open the url in the in app browser
Code Reproduction
Other Technical Details
Additional Context
The crashlytics report:
The text was updated successfully, but these errors were encountered: