I have 2 apps which uses BLE on same device. I have a BLE module to which I can connect without any issues. Covid Safe app is my 2nd app in device (loaded from App Store so I am not the owner of the code). I'm facing the same issue reported here when Covid app is running in background. I mean once my code centralManager.connectPeripheral(discoveredPeripheral, options: nil) is executed, it does not call its delegate methods didConnectPeripheral or didFailToConnect . But when the Covid app is killed or denied BLE permissions then my app is working fine. Mostly this is happening in iOS 13.x versions + iPhone X and above models

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

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.

@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 ??

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

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 ?