Norman Breau

> Below is the detailed crash log. Thanks the stacktrace helps associate the kind of bug, it should be resolved by #781 but the PR needs some work I think.

[stringByRemovingPercentEncoding](https://developer.apple.com/documentation/foundation/nsstring/1409569-stringbyremovingpercentencoding) and [stringByAddingPercentEncodingWithAllowedCharacters](https://developer.apple.com/documentation/foundation/nsstring/1411946-stringbyaddingpercentencodingwit) are both iOS 7+ so compatibility wise it should be fine. The newer APIs gives a warning... `stringByRemovingPercentEncoding`: > You must call this method only on strings...

I don't think it's really as simple as throwing in a `--https` flag. Using the HTTPS module is one thing, but it also needs a key/certificate pair. That could potentially...

It's possible that the blank screen you're seeing is the splashscreen without the icon resource being rendered, which is a bug within the android platform. The splash screen will be...

Thanks. Yah that's a strange one, that black screen isn't the splashscreen. If it was, it would have been black immediately before seeing your application view, and then typically the...

> Relating to the Android platform bug in https://issuetracker.google.com/issues/205021357, > > I saw that someone listed a possible fix in comment 69 for the icon not displaying when launching the...

> Hi! I’d like to work on this issue. Could you please assign it to me? > > Thanks! PRs are welcome, regardless of the assigned user.

There's a few things to unpack here, most of which doesn't make much sense: > /storage/emulated/0/Android/data/com.hablamedecristo.himnario2/files/test.mp3 This path suggests that you have your `test.mp3` stored in the `cordova.file.dataDirectory` and that...

> Where are you getting your information about applicationStorageDirectory being read only? My apologies, I got confused between `applicationStorageDirectory` and `applicationDirectory`. You're right that `applicationStorageDirectory` is a writable path. >...

> I suspect any https://localhost/ URL would give me this error. You're suspicion is right. It seems like the plugin is passing through the `https://localhost` url through to the underlaying...