-
Notifications
You must be signed in to change notification settings - Fork 361
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
Swizzling delegate sometimes blocks callback #48
Comments
Thanks - I'll look into it. You are leveraging |
I am not sure what you mean. In didFinishLaunching, I am doing this, and only this, to take advantage of TrustKit: Edit: So yea,
|
Yes, |
Okay. As I wrote in the topic that's also the solution I'm using. Honestly I don't know how else to do it :) |
The other solution is to manually call into |
Ah, okay. But the swizzling is a lot easier than that, and I don't need to do anything custom. Please let me know if you want me to debug anything on 1.3 (and in that case explicitly what). Sent from my iPhone On 31 May 2016, at 19:38, Alban Diquet <notifications@github.commailto:notifications@github.com> wrote: The other solution is to manually call into TSKPinningValidator to validate the server certificate in your connection delegates; it's described at the end of the "Getting Started" guide. By the way you have kTSKDisableDefaultReportUri enabled but if you have interest, you're free to use our dashboard for reviewing the reports. — |
I am not able to reproduce this so far. Which version of AFNetworking are you using? |
I'm sorry, I didn't receive any email indicating you had posted here (or I missed it). I use the latest version; 3.1.0. Edit: To point you in the direction of the problem; it does not happen for the "cached" validations. I'm not sure how the system works, but it seems that it does not validate the PIN for every single request. I.e. on 1.3 I'd get 3-4 good requests and then it would hang on the 5th as described in the original post. I would try the connection operation again (pull to refresh for instance) and it would succeed and then give me another 3-5-6 good requests before it would hang again. That being said it seems to be a bit more random than this, so it could take a few tries to get it to hang. It happens across all of the different views in my app, indicating that it's not just a stand-alone issue for a single view controller. Updating basically breaks my entire app. |
No worries. I think I know what the bug is; thanks for the help. |
You're welcome. I'll add 1.3.1 to my project and test it out once it's available through Pods. |
1.3.1 is on Pods now. Let me know if you still see the same issue. |
Hello
After updating to 1.3 I have some random issues with delegate callbacks not happening.
The network connection object is created, configured, resumed and the console prints:
And then nothing happens. No error callback, no success either, My app just remains in the loading state forever, confusing users.
I did clean/build and emptied derived data folder. No change. Downgrading to 1.2.5 seems to fix the problem. I use NSURLSession with AFNetworking.
On another note, the console prints:
On launch, instead of the algorithms I specified in the config, like:
kTSKPublicKeyAlgorithms : @[kTSKAlgorithmRsa2048],
I don't know if that's an error, but it seems odd to me.
Edit: It seems it does not affect iPads. I don't really see any patterns to it. Observed on (different) iPhones with iOS 9.3.1 (and Simulator). If I remove TrustKit entirely it goes away, and as I said it also does not happen on 1.2.5.
The text was updated successfully, but these errors were encountered: