Found this [link](https://www.nccgroup.trust/globalassets/newsroom/us/blog/documents/2015/01/bypassing_openssl_pinning.pdf) online. (Refer Page #8) Not really sure how to prevent changing value from SSL_VERIFY_PEER to SSL_VERIFY_NONE. Do we have any ways to programmatically get the current value of SSL_CTX_set_verify set ?

Yes after this, using Burp suite we can monitor the network traffic. But without this, Burp suite could not monitor network.

@Claude31, In my case, the module is my iOS Framework. I have very few Swift files (say less than 5) Not doing anything with Swift 5.5 APIs. All other files are Obj-c files. As you told, if Module stability is Upward compatible only.. Then does it mean, a framework project having minimum deployment target as iOS 11 and compiled & built using Xcode 13 cannot be used in an iOS project built using Xcode 12.4/ 12.5/12.5.1 as they have lower version of Swift 5.5 ??

May be a bad approach, but just sharing this. I am not really sure why import _Concurrency getting added in the file arm64-apple-ios.swiftinterface located in our swiftmodule folder. Open that file and Just comment this import statement and this error disappears.

Same here.. To make the issue more clear i simply created a Hello world app and tried to submit. Got the same error.