-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Certificate trust Issue #1419
Comments
Not sure what can cause it. This error is given out by Is this happening on the same device with the same settings? Say, good for a while, and then failed later on? Or is it happening on different devices? I suggest you can check:
|
same issue |
Hi, @aerialkoala did you see the comment before , ref : #226 . Implement extension of UIImageView, you can call the setImage function, in other places.
How do we use
And you can implement another class,
At last, you may set Run the project and watch the console, if print any debug info there. Hopefully, it will work for you. |
There is actually some sample code in the wiki: https://github.com/onevcat/Kingfisher/wiki/Cheat-Sheet#authentication-with-nsurlcredential But it is surprising that you need to set it to |
Maybe your |
Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.
Issue Description
Invalid certificate Issue
What
I am part of iOS developer group from USBank and we are using Kingfisher for our image rendering and caching mechanisms. We have some public facing image URL in the app for example(https://www.usbank.com/dam/images/nba/anticipate/template6/HELOC_Illustration3x.png). The issue is the image is getting rendered sometimes but the same image url is giving us back the certificate issue. I couldn't understand what exactly is causing this issue. I know adding "www.usbank.com" as trusted domain works but If you can guys provide a reason why it's failing sometimes it would be helpful for me to answer my management. The user experience in this error scenario is very bad from app perspective.
Complete Error details:
A URL session error happened. The underlying error: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “www.usbank.com” which could put your confidential information at risk." UserInfo={NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, NSErrorPeerCertificateChainKey=(\n "<cert(0x7ff11009e000) s: www.usbank.com i: web-proxy.us.bank-dns.com>",\n "<cert(0x7ff11002d800) s: web-proxy.us.bank-dns.com i: web-proxy.us.bank-dns.com>"\n), NSErrorClientCertificateStateKey=0, NSErrorFailingURLKey=https://www.usbank.com/dam/images/nba/anticipate/template4/HELOC_Illustration3x.png, NSErrorFailingURLStringKey=https://www.usbank.com/dam/images/nba/anticipate/template4/HELOC_Illustration3x.png, NSUnderlyingError=0x6000023d0300 {Error Domain=kCFErrorDomainCFNetwork Code=-1202 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x600001e60c60>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9813, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9813, kCFStreamPropertySSLPeerCertificates=(\n "<cert(0x7ff11009e000) s: www.usbank.com i: web-proxy.us.bank-dns.com>",\n "<cert(0x7ff11002d800) s: web-proxy.us.bank-dns.com i: web-proxy.us.bank-dns.com>"\n)}}, _NSURLErrorRelatedURLSessionTaskErrorKey=(\n "LocalDataTask <6726D1C3-B2DB-4A31-BADD-D825E03547EC>.<1>"\n), _kCFStreamErrorCodeKey=-9813, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <6726D1C3-B2DB-4A31-BADD-D825E03547EC>.<1>, NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x600001e60c60>, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “www.usbank.com” which could put your confidential information at risk.}
We are using version 5.6
We are rending this image inside a view controller.
xcode version 11.3
Thanks in advance.
The text was updated successfully, but these errors were encountered: