Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug: #2393

Closed
1 of 4 tasks
barrcodes opened this issue Jan 30, 2020 · 12 comments
Closed
1 of 4 tasks

bug: #2393

barrcodes opened this issue Jan 30, 2020 · 12 comments

Comments

@barrcodes
Copy link

barrcodes commented Jan 30, 2020 •
edited
Loading

Bug Report

Capacitor Version

npx cap doctor output:
Latest Dependencies:

@capacitor/cli: 1.4.0

@capacitor/core: 1.4.0

@capacitor/android: 1.4.0

@capacitor/ios: 1.4.0

Installed Dependencies:

@capacitor/core 1.4.0

@capacitor/cli 1.4.0

@capacitor/android 1.4.0

@capacitor/ios 1.4.0

Affected Platform(s)

  • Android
  • iOS
  • Electron
  • Web

Current Behavior

I require a secure server connection to use a library which requires web crypto (auth0). To do so, I am running live-reload on android using ionic capacitor run android -l --external --ssl. This starts a secure server at https://my.ip.address:8100

My app launches, the splash screen loads, and then the splash screen times-out to a blank white page with no content:

<html>
    <head></head>
    <body></body>
</html>

I receive no error logs in Android Studio or in chrome developer tools.

The application loads fine in browser when I navigate to the url.

Expected Behavior

I expect the app to load normally.

Reproduction Steps

  • Create Android capacitor project
  • Run ionic capacitor run android -l --external --ssl
  • Try to run the project on the Android emulator
  • Blank screen

Other Technical Details

npm --version output: 6.13.4

node --version output: v13.5.0
@jcesarmobile
Copy link
Member

that's because the webview won't allow navigation if using self signed certificates, and that's something we won't allow.
But we are working in making the WebViewClient configurable or let plugins implement some of it's methods so you users can use it for allowing self signed certificates (under their own risk) , see #2230

@barrcodes
Copy link
Author

barrcodes commented Jan 31, 2020 •
edited
Loading

I also found some info about manually signing a certificate using your own certificate authority, and then adding that certificate authority to Android via the security settings. However, this was complicated, and I got stuck.

I ended up solving this in a way that allowed me to not use https when debugging locally. But I'm looking forward to the feature you mentioned.

@barrcodes
Copy link
Author

@jcesarmobile sorry ahead of time if this sounds rude. This is a bug with a potential feature solution that has not yet been solved. It should not be closed until the feature is implemented, and a solution is tested.

Because this bug is referenced in your feature, it can be automatically closed on a merged PR. Closing this issue only artificially deflates your # of open issues, and makes it more difficult for developers with the same issue to search.

@jcesarmobile
Copy link
Member

jcesarmobile commented Jan 31, 2020 •
edited
Loading

no, not allowing self signed certificates is not a bug, sorry.

There is an issue to allow users to change the WebViewClient and it's open, so track that one.

@barrcodes
Copy link
Author

barrcodes commented Jan 31, 2020 •
edited
Loading

@jcesarmobile the issue (or bug) is: live reload with the external and ssl flags does not work on Android because self-signed certificates are not allowed.

There is absolutely a bug. And your proposed feature very well could fix it.

If your team decided not to prioritize the feature that you suggested, this bug could be closed with no solution and a "self-signed certificates are not on the road map"

@jcesarmobile
Copy link
Member

live reolad with ssl flag is an ionic feature, not a capacitor feature, so again, this is not a capacitor bug

@fxdave
Copy link

fxdave commented Feb 4, 2021

I'm not using ionic. How can I test deep linking locally?
I spent at least a day making an HTTPS reverse proxy with a self-signed certificate, with some DevOps stuff to make it easier for my teammates. And it's all because the documentation says deep linking works only on HTTPS.
And now I read this, and I turn to be sad because of a whole worthless day.

@jcesarmobile
Copy link
Member

This issue has nothing to do with deep linking.

Deep linking requires uploading some files that associate your website with your app. Your website needs to use https, not the app.

@pencilcheck
Copy link

pencilcheck commented Mar 14, 2022 •
edited
Loading

that sucks, if it is not capacitor, then why is capacitor having documentation on live reload?
https://capacitorjs.com/docs/guides/live-reload

This should have a updated text saying that "haha, we are just fooled you, it is actually ionic stuff not capacitor" and reference this link in the page.

I wasted hours and found this thread. Funny thing is, capacitor is under the ionic flag, somehow it is not supported. that just doesn't make any sense from a consumer point of view.

@KthProg
Copy link

KthProg commented Apr 1, 2022

So where should we mention this bug since this breaks development and needs a solution from someone?

@KthProg
Copy link

KthProg commented Aug 16, 2022

Hello, any idea who we would talk to / where we would create an issue with ionic since this is not an ionic capacitor bug but instead just an ionic bug?

@ionitron-bot
Copy link

ionitron-bot bot commented Nov 10, 2022

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.

@ionitron-bot ionitron-bot bot locked and limited conversation to collaborators Nov 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pencilcheck @barrcodes @jcesarmobile @KthProg @fxdave