Afnetworking: Version 3.2.0 having Issue with Setting AFSecuirity Policy , "A security policy configured with `%@` can only be applied on a manager with a secure base URL (i.e. https)" same code working in 3.1.0 version.

[kamabhavik]

I am using AFNetworking version 3.2.0.In my app am using SSL Pining with certificate.

Recently when I have updated my AFNetworking pods from 3.1.0 to 3.2.0 then my SSL Code stopped working with throwing exception with "A security policy configured with %@ can only be applied on a manager with a secure base URL (i.e. https)".

Please guide me if am doing something wrong or is there anything else I need to improve upon.

[raistlin969]

I have this as well, wondering if it is related to issue #4141

[petrinichav]

+1 Looks that you have baseURL == nil or http instead https

[Brukhan]

+1 I also have same issue. It worked before.

[CoderSimonWong]

+1

[Yelles]

+1, rollback back for me to the 3.1.0 version...

[czh0318]

Init you session manager by this way:
AFHTTPSessionManager * manager = [[AFHTTPSessionManager alloc] initWithBaseURL:[NSURL URLWithString:]];

[lizhaojie001]

I think it's come from other libs

[duduWang20]

Yes . It is a feature of 3.2.0 , you should use https or pinning none , http with other pinning mode is invalide .

[kamabhavik]

@wangjufan But I am already using https url

[Yelles]

@wangjufan i’m already in full https & pinning mode...

[duduWang20]

Check the baseURL , it can't be nil .

[nikunjazilen]

@wangjufan Facing issue in latest pod version: 3.2.1. A security policy configured with %@ can only be applied on a manager with a secure base URL. Is it resolved or not?

[RunerZhang]

同样的问题 回退到3.1就正常了

[CoderSimonWong]

@RunerZhang 设置基础 base URL，就没有问题了

[marcocattai]

any news on this?

[stale[bot]]

This issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale[bot]]

This issue has been auto-closed because there hasn't been any activity for at least 21 days. However, we really appreciate your contribution, so thank you for that! 🙏 Also, feel free to open a new issue if you still experience this problem 👍.

[jleisurely]

Init you session manager by this way:
AFHTTPSessionManager * manager = [[AFHTTPSessionManager alloc] initWithBaseURL:[NSURL URLWithString:]];

it is a beat way to solve this problem