-
Notifications
You must be signed in to change notification settings - Fork 1k
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 does not initialised when server.url uses ssl on Android #6291
Comments
Any update on this please? It's a blocker at the moment |
the sample app you provided requires user/password that are not provided on the steps to reproduce, can you provide them? |
Changed, it should work now without credentials |
the provided url doesn't return anything, Capacitor only injects itself in html pages with a head tag |
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
Current Behavior
Given a project with
appendUserAgent
andserver.url
pointing to a https link:Capacitor does not initialised, hence it's not available in the global window object:
Expected Behavior
Capacitor should get initialised and injected in the global window once the link gets rendered as it happens on iOS:

Code Reproduction
Check here the steps to reproduce it.
Other Technical Details
npm --version
output: 6.14.8node --version
output: v12.20.0Additional Context
Worth to mention I explicitly need
appendUserAgent
property. In some cases it looks it works pointing to a different https link. But in some others,overrideUserAgent
is the only way to make it work. So depending on the link and theuserAgent
value Capacitor gets available or not.I check related issues: #3707, #7234, #5354 but I don't spot any similarity.
In this case I don't see any log related to a SSL issue nor to a problem on the Bridge at some point. In fact, I always see the plugins get registered without errors and the app gets started:
("System WebView is not supported" is a debug log when the Android version is not the minimum one, but it does not prevent the app to get started. Other links with the same log work)
However, Capacitor is not available once the link is rendered, in contrast to iOS where it works seamlessly.
I tried with different Android devices on the emulator and BrowserStack but I always get the same issue.
The text was updated successfully, but these errors were encountered: