Update to HttpClient breaks images with CORS restrictions on iOS with WKWebView

[vegardlarsen]

See #125.

This merge appears to break image loading on iOS with WKWebView. It happens because there is no way to disable CORS when you are using WKWebView.

In my case, the images I would like to cache for offline use are user avatars, which means that I do not control the remote server and cannot work around the issue that way.

Downgrading to 4.2.1 fixes the issue for now.

[ihadeed]

Thanks for reporting this bug.

Are you having the CORS issues when trying to download the images from the remote server? or when trying to load them from the filesystem?

[vegardlarsen]

They occur when loading from the remote server, and the spinner is displayed forever.

[glemiere]

I confirm! v5.0.0 using WKWebView result in CORS issues for picture loaded remotely.
Downgrading to 4.2.1 is fixing the problem.

[ihadeed]

See https://ionicframework.com/docs/wkwebview/#xhr-requests-do-not-work

Looks like we have to revert the HttpClient change, or seek an alternative. I'm leaning more towards my WIP native http plugin, but I'm not sure when I'll have time to finish developing it.

[Boldonglen]

I have the same issue displaying an image from a remote server on an iOS device. Do we know when this fix will be implemented. I tried downgrading to v4.2.1 but was still getting the issue. What's the correct procedure for downgrading?

[glemiere]

@Boldonglen change the version of the package in your package.json, then run npm install.
If it's still doesn't work then you should look into the configuration of the server serving your pictures.

[Boldonglen]

Hi @glemiere, Thanks for the advice ill try that. I have full control of the server and I use NGINX to host my PHP (Laravel) backend that serves up the images. Could you give me any advice on how the it should be configured?

[glemiere]

@Boldonglen you can enable CORS in PHP using the following header :

header("Access-Control-Allow-Origin: *");

You can directly apply this header to your nginx configuration, see :
https://gist.github.com/Stanback/7145487

[matheusdavidson]

same here.

My pictures are on amazon S3, i tried to change the CORS config but wasn't successful. Had to downgrade to 4.2.1.

[glemiere]

@matheusdavidson you have no CORS issues on your server as long as downgrading to 4.2.1 works. If it doesn't, only then you might have a real CORS issue ;)

[jaybloke]

Also had to downgrade to 4.2.1 to get this to work with S3 (CORS config is correct). However, periodically, images not loading - probably because of other issues with WKWebView compatibility(?).

This is a dealbreaker for me - I would rather let users sit and wait for images to reload rather than not show anything! Hasten to say, I've dropped this plugin :-(

Totally agree with @ihadeed on reverting/finding an alternative to HttpClient.

[mtshare]

@jaybloke same for me with S3 images loading. Downgraded to 4.2.1 and it works.