Configuring FFImageLoading's HttpClient throws a null reference exception

I just updated from 2.7.2 to 3.1.0 and noticed the following configuration throws a null reference exception on Android.

Add this to MainActivity:

var configuration = new Configuration
{
	FadeAnimationEnabled = false,
	HttpClient = new System.Net.Http.HttpClient(new NativeMessageHandler())
};

I’m using FFImageLoading 2.4.11.982 and XF 4.

Adding @daniel-luberda in case this issue belongs to his code.

[Pinox]

@alexrainman ,

Please consider an escape hatch in ModernHttpClient for guys that would like a less aggressive approach to security. Certificate pinning sounds good in theory but has significant inherent risks. When pinning a public key chain , we are assuming that the certificate authority, it’s intermediate certificates and your leaf certificate do not change.

So if you are not careful in your execution of renewing your certificate or if your certificate provider suddenly change their certificate then you are stuck as your public keys will change in such instances. Also, if your keys get compromised or if god forbid you lose them then you are forced to change your public key, so now you have to think about backup keys otherwise your users won’t be able to access your site.

In my opinion going offline is a much more severe threat than getting exposed to a sophisticated man-in-the-middle attack.

Google initiated certificate pinning and eventually abandoned it because of the lack of an build-in recovery mechanism. I know you stated version 2.7.2 is good but then many users will be stuck if something “new” breaks it.

[alexrainman]

Yes. I removed 3.x iterations as i am not planning to update this for a while.

Good to know it works as expected.