Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
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
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
live reolad with ssl flag is an ionic feature, not a capacitor feature, so again, this is not a capacitor bug
@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.