-
Notifications
You must be signed in to change notification settings - Fork 371
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
[Bug] No longer working #321
Comments
UPDATEI've created a test repo in attempt to reproduce the issue, but still can't: My latest investigation revealed that the execution does not enter TrustKit's Is there anything I might have missed here? Test Repo (entering TrustKit methods ✅)XCode Debug stack trace
iOS -> MacOS console log (hard to capture, it flows non-stop and won't pause)
Original Repo (not entering TrustKit methods ❌)XCode Debug stack trace
iOS -> MacOS console log (hard to capture, it flows non-stop and won't pause)
|
Hi,
About 1-2 months ago, I had used this library through react-native-ssl-public-key-pinning to enforce SSL pinning in my company's app on a PoC branch, which worked as expected.
And just yesterday, I tried to install and apply the library again in a new branch, but now it does not block any request to pinned domain when using invalid keys.
I'm not sure if this was the issue with
react-native-ssl-public-key-pinning
or with the TrustKit, but the configuration used to initialize TrustKit looks supposedly correct. (I also opened an issue there)Logs
(iOS to MacOS Console log)
Versions
TrustKit: 3.0.3
CocoaPods: 1.14.3
iOS: 16.2 (iPhone Simulator)
Thanks!
The text was updated successfully, but these errors were encountered: