CFNetwork

RSS for tag

Access network services and handle changes in network configurations using CFNetwork.

CFNetwork Documentation

Pinned Posts

Posts under CFNetwork tag

153 Posts
Sort by:
Post not yet marked as solved
2 Replies
1.2k Views
I have this basic get request when I call it in app I receive the error below. When I run it in playgrounds I get the same error let url = DevAPI.BaseURL.submitted guard let requestUrl = url else { fatalError() } var request = URLRequest(url: requestUrl) request.httpMethod = "GET" let tokenString = UserDefaults.standard.string(forKey: "name") ?? "" request.setValue(tokenString, forHTTPHeaderField: "x-access-token") let session = URLSession.shared session.dataTask(with: request) { (data, response, error) in if error != nil { 	  print("error :::", error)  	 } else {         print("no error", response)     } }.resume() This request is never making it to the server as in the logs I don't see anything show up when its made. 2020-12-23 12:29:37.817028-0500 Hammoq[63627:1122236] Task <9EAC71EE-DA88-4356-A180-D843E89CC7B9>.<1> finished with error [303] Error Domain=kCFErrorDomainCFNetwork Code=303 "(null)" UserInfo={_NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <9EAC71EE-DA88-4356-A180-D843E89CC7B9>.<1>, _kCFStreamErrorDomainKey=4, NSErrorPeerAddressKey=<CFData 0x600003820f50 [0x7fff8002e8c0]>{length = 16, capacity = 16, bytes = 0x100201bb23b852d00000000000000000}, _kCFStreamErrorCodeKey=-2205, _NSURLErrorRelatedURLSessionTaskErrorKey=(     "LocalDataTask <9EAC71EE-DA88-4356-A180-D843E89CC7B9>.<1>" )} error ::: Optional(Error Domain=kCFErrorDomainCFNetwork Code=303 "(null)" UserInfo={_NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <9EAC71EE-DA88-4356-A180-D843E89CC7B9>.<1>, _kCFStreamErrorDomainKey=4, NSErrorPeerAddressKey=<CFData 0x600003820f50 [0x7fff8002e8c0]>{length = 16, capacity = 16, bytes = 0x100201bb23b852d00000000000000000}, _kCFStreamErrorCodeKey=-2205, _NSURLErrorRelatedURLSessionTaskErrorKey=(     "LocalDataTask <9EAC71EE-DA88-4356-A180-D843E89CC7B9>.<1>" )}) If I use a different url from the same db I don't receive any errors. Another strange thing is that if I remove the header "x-access-token" I do not get the error and instead get response 403 which makes sense.
Posted
by
Post not yet marked as solved
12 Replies
1.9k Views
Hi, The article https://developer.apple.com/news/?id=g9ejcf8y "Identity Pinning: How to configure server certificates for your app" from 2021-01-14 looks really promising. However, I cannot get the settings to have any effect on iOS 14.3 (Xcode 12.3). I tested with NSPinnedCAIdentities and Charles Proxy as well as an incorrect RootCA key. In both cases the requests were successful, Charles was able to decrypt the traffic. Questions that come to my mind: Where is the detailed documentation of the keys? Which platforms/versions are supported? Thanks and kind regards, Lars
Posted
by
lpe
Post not yet marked as solved
8 Replies
1.9k Views
Hi, im making a daemon swift app for macos that uses the content filter network extension. When i run the app i see the following leak in Instruments. 2021-03-08 15:58:54.943753-0300 mhunt[23320:342851] [] nw_parameters_copy_default_protocol_stack called with null parameters 2021-03-08 15:58:54.950468-0300 mhunt[23320:342851] [] nw_parameters_copy_default_protocol_stack called with null parameters, dumping backtrace: [x86_64] libnetcore-2288.80.2 0 libnetwork.dylib 0x00007fff247c82f8 __nw_create_backtrace_string + 120 1 libnetwork.dylib 0x00007fff242bb69b nw_parameters_copy_default_protocol_stack + 251 2 libnetwork.dylib 0x00007fff242dea0e nw_socket_connect + 1550 3 libnetworkextension.dylib 0x00007fff300c6102 ne_filter_protocol_connect + 396 4 libnetworkextension.dylib 0x00007fff300c73dc ne_filter_process_verdict + 1616 5 libnetworkextension.dylib 0x00007fff300cb5f7 __ne_filter_data_protocol_send_new_flow_block_invoke.65 + 148 6 libdispatch.dylib 0x000000010b5e8e78 _dispatch_call_block_and_release + 12 7 libdispatch.dylib 0x000000010b5ea0b0 _dispatch_client_callout + 8 8 libdispatch.dylib 0x000000010b5f406a _dispatch_workloop_invoke + 3277 9 libdispatch.dylib 0x000000010b600217 _dispatch_workloop_worker_thread + 1675 10 libsystem_pthread.dylib 0x000000010b693b15 _pthread_wqthread + 314 11 libsystem_pthread.dylib 0x000000010b692ae3 start_wqthread + 15 I have no idea how to debug this. As you can see on the log it says "libnetworkextension" so i thought i might have something to do with the network extension but the leak ocurrs even when the NE is not running. I tried looking at the memory graph but when i go to click on the memory address that has the leak all i see is an icon of "OS_dispatch_group". I know this might be not enough information to help me debug this so if you need anything else just let me know.
Post not yet marked as solved
6 Replies
1k Views
Hi, I implemented the NSPinnedDomains according to https://developer.apple.com/news/?id=g9ejcf8y "Identity Pinning: How to configure server certificates for your app". This is my config (I added a wrong SHA256 hash so I can test if it works): keyNSAppTransportSecurity/key dict     keyNSPinnedDomains/key     dict         keyjsonplaceholder.typicode.com/key         dict             keyNSPinnedCAIdentities/key             array                 dict                     keySPKI-SHA256-BASE64/key                     stringr/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=/string                 /dict             /array             keyNSIncludesSubdomains/key             true/         /dict     /dict /dict With NSURLSessions it properly fails when I try to load https://jsonplaceholder.typicode.com/todos/2 it prints following error: An SSL error has occurred and a secure connection to the server cannot be made But when I try to load the URL from JavaScript in WKWebView, it succeeds. Is WKWebView not supported? Or am I doing something wrong? Thanks and kind regards, Mika Objc code: NSString *urlString = @"https://jsonplaceholder.typicode.com/todos/2"; NSURL *url = [NSURL URLWithString:urlString]; NSURLSessionDataTask *downloadTask = [[NSURLSession sharedSession] dataTaskWithURL:url completionHandler:^(NSData *data, NSURLResponse *response, NSError *error) { }]; [downloadTask resume]; Web code (can be included in any html page inside WKWebView): script document.addEventListener("DOMContentLoaded", () = { fetch("https://jsonplaceholder.typicode.com/todos/2") .then(res = res.json()) .then(res = console.log(res)); }); /script
Posted
by
Post not yet marked as solved
4 Replies
879 Views
Hi All, I wanted to perform the upload task in the background using a URLSessionConfiguration background session and after that, once the upload is done, I have to send the status API call to the server again. I have implemented the URLSession with background configuration and it is working fine and uploaded the file in the background or suspend state and invoke the app in the background with delegate. After uploading the file, I'm sending the status call to the server but it is not working and looks like the app is invoked for a few seconds and again went to the suspend state. Please suggest, how will I send status calls after the app invokes in the background for upload completion. Thanks in advance.
Posted
by
Post not yet marked as solved
7 Replies
3.7k Views
After starting using Xcode 13 beta(1 and 2) and iOS15 simulators we realized that we can't connect to our internal servers using https connection with self-signed certificate. We are receiving NSUnderlyingError=0x600003f91e30 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x6000000f4e60>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9802, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9802 At the moment we don't have any devices with iOS15 beta installed on them and couldn't confirm if issue reproduced there as well but using simulator or real devices with prior versions of iOS works without any issues and we are not sure if it's a bug in iOS15 beta builds or some new security restrictions for SSL/TLS connections or trusted connections. We are using certificate pinning(and including and using root certificate) and couldn't see any issues while validating SecTrust object after receiving challenge inside URLSessionDelegate let host = challenge.protectionSpace.host       guard challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodServerTrust,          let trust = challenge.protectionSpace.serverTrust       else {         completionHandler(.performDefaultHandling, nil)         return       }               let policy = SecPolicyCreateSSL(true, host as CFString)       let status = SecTrustSetPolicies(trust, policy)       let pinCertificate = SecTrustSetAnchorCertificates(trust, certificates as CFArray)       let onlyStatus = SecTrustSetAnchorCertificatesOnly(trust, true)               var error: CFError?       let isValidationSuccessful = SecTrustEvaluateWithError(trust, &error)       if isValidationSuccessful {         completionHandler(.useCredential, URLCredential(trust: trust))       } else {         completionHandler(.cancelAuthenticationChallenge, nil)       } Could someone clarify next questions: What does 9802 error code actually mean? i found that it some kind of generic fatal error but it isn't useful information Are there any new restrictions for self signed certificates or ssl/tls connections that will be introduced in iOS15?
Posted
by
Post not yet marked as solved
1 Replies
343 Views
I'm working on a project that uses URLSession with a client certificate authentication of HTTP requests. In case of an authentication error, I need to know the exact cause of the SSL error. Unfortunately, the task callback error only returns a "Connection lost" status and does not contain any useful information in the underlying error. Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={_kCFStreamErrorCodeKey=-4, NSUnderlyingError=0x1007cc780 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 "(null)" UserInfo={NSErrorPeerAddressKey=&lt;CFData 0x109c08a50 [0x7fff8066ab70]&gt;{length = 16, capacity = 16, bytes = 0x100201bb3369e6040000000000000000}, _kCFStreamErrorCodeKey=-4, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask &lt;E0F9E193-0CE8-4B42-9E46-72166BA54F2A&gt;.&lt;1&gt;, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask &lt;E0F9E193-0CE8-4B42-9E46-72166BA54F2A&gt;.&lt;1&gt;" ) In the console logs, I can see what caused the error. For example, if the certificate is omitted: Error: 4454414168:error:1000045c:SSL routines:OPENSSL_internal:TLSV1_CERTIFICATE_REQUIRED:/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-351.100.9/ssl/tls_record.cc:594:SSL Is there any way to retrieve that information without using a lower-level framework?
Posted
by
Post marked as solved
6 Replies
781 Views
class  a {     b().download ({ data in     }) } class  b{     func download (downloadedData: @escaping (_ data: Data? ) -&gt; Void )  {         c().download()     } } class c {     func download () -&gt; Data {         let semaphore = DispatchSemaphore(value: 0)           NetworkManager().downloadRequest: { (result: Result&lt;Data, Error&gt;) in                                             switch result {                                             case .success(let success)                                                 ......                                              case .failure(let error): .....                                             }                                             semaphore.signal()                                    }                         )         semaphore.wait()         return data     } } Class a initiates the download and class c interacts with network manager to download the data. Class c issues semaphore wait as soon as it sends request to download the data and issues signal when download completes. Is there a way to issue signal from class a when download is in progress. Basically class a should be able to skip wait by issuing signal command
Post not yet marked as solved
1 Replies
327 Views
We have certificate pinning for our app used by millions of customers, and we recently moved from using an Amazon CA to our company custom CA certificate. We followed the following these steps: Include a copy of the certificate authority's root certificate in the app Once you have the trust object, create a certificate object from the certificate data (SecCertificateCreateWithData) and then set that certificate as a trusted anchor for the trust object (SecTrustSetAnchorCertificates) SecTrustSetAnchorCertificates sets a flag that prevents the trust object from trusting any other anchors, if you also want to trust the default system anchors, call SecTrustSetAnchorCertificatesOnly to clear that flag Evaluate the trust object as per usual SecTrustEvaluate returns .unspecified and we call completionHandler(.useCredential, credential) on the completion handler for urlSession:didReceive:completionHandler. However, the error we get is: Domain=NSURLErrorDomain Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, NSErrorPeerCertificateChainKey=(   "&lt;cert(0x12e0e8800) s: mydomain.com i: mydomain.com&gt;" ), NSErrorClientCertificateStateKey=0, NSErrorFailingURLKey=https://mydomain.com/xxxxx, NSErrorFailingURLStringKey=https://mydomain.com/xxxxx, NSUnderlyingError=0x283885110 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=&lt;SecTrustRef: 0x2804e15f0&gt;, _kCFNetworkCFStreamSSLErrorOriginalValue=-9802, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9802, kCFStreamPropertySSLPeerCertificates=(   "&lt;cert(0x12e0e8800) s: mydomain.com/xcom i: mydomain.com&gt;" )}}, _NSURLErrorRelatedURLSessionTaskErrorKey=(   "LocalDataTask &lt;56BD63E5-3D28-4EBF-83DC-C11C744DF4E4&gt;.&lt;1&gt;" ), _kCFStreamErrorCodeKey=-9802, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask &lt;56BD63E5-3D28-4EBF-83DC-C11C744DF4E4&gt;.&lt;1&gt;, NSURLErrorFailingURLPeerTrustErrorKey=&lt;SecTrustRef: 0x2804e15f0&gt;, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made.} The only solution so far was to install the certificate on the simulator then it worked. However, we are not in a position to get customers to install the certificate - whether via MDM or otherwise. Is there a seamless solution for using custom certificates as I don't think Apple recommends (or even allows nowadays) to add exception domains in the plist?
Posted
by
Post marked as solved
1 Replies
316 Views
Hello, tldr; relaunch for background uploads isn't working as expected. I'm testing my code on iPad OS 14.6 and XCode 12.5.1. Background app refresh is ON on my device for my app. A background file upload is being setup with URLSession. The URL session is created as soon as the app starts up and not lazily created. See URL session configuration below. I have followed the test instructions as outlined here: https://developer.apple.com/forums/thread/14855, specifically launching my app not via Xcode but from the home screen and adding an exit() call after the app enters the background in the AppDelegate callback method applicationDidEnterBackground. The file transfer is initiated before the app enters the background. Here's the configuration code I'm using: let configuration = URLSessionConfiguration.background(withIdentifier: &lt;unique_identifier&gt;)     configuration.sessionSendsLaunchEvents = true     configuration.sharedContainerIdentifier = &lt;container group identifier&gt;     configuration.isDiscretionary = false     configuration.timeoutIntervalForResource = 3600 * 24 * 2 // wait for 2 days before timing out connections                urlSession = URLSession(configuration: configuration, delegate:self, delegateQueue: nil) The file in fact finishes uploading but the app isn't relaunched as one would expect. As soon as I re-open the app from the home screen, I get the requisite callbacks about the upload having completed properly. In the past when I have tested my code, the method AppDelegate:handleEventsForBackgroundURLSession used to be called after the upload finishes. That appears to no longer be the case. Any guidance/help will be hugely appreciated! Thanks Krishna
Posted
by
Post marked as solved
1 Replies
324 Views
Hi, I have an app that has been online for a long time, but a very small number of users will respond with "-1009, the internet connection appears to be offline" error, but most users are normal, which may indicate that it is a device problem. The user's network uses 4G, and the user indicates that it is normal to connect to other apps. In my opinion, if my App uses URLSession to get this Error, other apps should also get it, and all apps cannot make network requests, but it is not. Currently I always ask users to restart the network or use wifi, but this may not solve this problem. Maybe the device has other network settings that can cause this problem? (The user did not use the flight mode) Anyone know any solutions or know this problem?
Posted
by
Post marked as solved
1 Replies
734 Views
I faced the below issues in my request logs, the users who have reported this only on iOS 14.6 iOS 14.7 , I do not understand why. only found on iOS 14.6 and iOS 14.7 https://developer.apple.com/documentation/cfnetwork/kcferrordomaincfnetwork https://developer.apple.com/documentation/cfnetwork/cfnetworkerrors/kcferrorhttpsproxyconnectionfailure?language=objc AFN Version: 4.0.1 error logs: Optional(Error Domain=kCFErrorDomainCFNetwork Code=310 "(null)" UserInfo={_NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask &lt;D47C60FA-62F4-4676-B504-B2C181C91263&gt;.&lt;8&gt;, _kCFStreamErrorDomainKey=4, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask &lt;D47C60FA-62F4-4676-B504-B2C181C91263&gt;.&lt;8&gt;" ), _kCFStreamErrorCodeKey=-2102}) How can I resolve this issue ? Thanks
Posted
by
Post not yet marked as solved
3 Replies
446 Views
Crashed: com.apple.NSURLSession-work 0 libobjc.A.dylib 0x1b1046dd0 objc_release + 16 1 libobjc.A.dylib 0x1b1026cd8 object_cxxDestructFromClass(objc_object*, objc_class*) + 112 2 libobjc.A.dylib 0x1b103e148 objc_destructInstance + 80 3 libobjc.A.dylib 0x1b10455c4 _objc_rootDealloc + 80 4 CFNetwork 0x19cb967e4 CFNetServiceBrowserSearchForServices + 14800 5 CFNetwork 0x19cba3df8 CFNetServiceBrowserSearchForServices + 69604 6 libdispatch.dylib 0x19c16da84 _dispatch_call_block_and_release + 32 7 libdispatch.dylib 0x19c16f81c _dispatch_client_callout + 20 8 libdispatch.dylib 0x19c177004 _dispatch_lane_serial_drain + 620 9 libdispatch.dylib 0x19c177c34 _dispatch_lane_invoke + 456 10 libdispatch.dylib 0x19c1824bc _dispatch_workloop_worker_thread + 764 11 libsystem_pthread.dylib 0x1e81fe7a4 _pthread_wqthread + 276 12 libsystem_pthread.dylib 0x1e820574c start_wqthread + 8
Posted
by
Post marked as solved
1 Replies
562 Views
I'm trying to upload an existing zip file to a server, but the file itself doesn't seem to be present in the request when I check what the server actually receives. Here's my current implementation: func uploadZip(filePath: URL, authorization: String, callback: @escaping ((Bool) -&gt; Void)) { BGUploadManager.callback = callback let url = URL(string: "\(APINetwork.BASE_URL)")! var request = URLRequest(url: url) request.headers = ["Authorization": "Bearer " + authorization] request.method = HTTPMethod(rawValue: "POST") request.setValue("application/zip", forHTTPHeaderField: "Content-Type") let config = URLSessionConfiguration.background(withIdentifier: "identifier") config.isDiscretionary = false let session = URLSession(configuration: config, delegate: self, delegateQueue: OperationQueue.main) let task = session.uploadTask(with: request, fromFile: filePath) task.resume() } There are implemented handlers for completion and progress and they work properly. The problem is really just the actual file not being sent (or if it is I don't know how to get it). Here's parts of what the server receives: headers: { host: 'localhost:1337', 'content-type': 'application/zip', 'accept-encoding': 'gzip, deflate', connection: 'keep-alive', accept: '*/*', 'user-agent': 'App/37 CFNetwork/1237 Darwin/20.4.0', authorization: 'Bearer sometokenhere', 'content-length': '89634' } body: {} Checking for request.files also shows that it's empty. The Content-Length value is correct. The filePath is the full path and does actually point to the zip file.
Posted
by
Post not yet marked as solved
1 Replies
441 Views
I always get this crash report when I try connecting to the webskocket using TwilioChatClient pod. I have tried to contact them but it wasn't very helpful. I can see that the crash happens in this line but I don't know the reason. -[__NSURLSessionWebSocketTask _onqueue_enableWebSocketFraming:] Thread 5 name: Thread 5 Crashed: 0 CFNetwork 0x000000018d252da0 -[__NSURLSessionWebSocketTask _onqueue_enableWebSocketFraming:] + 468 (LocalWebSocketTask.mm:223) 1 CFNetwork 0x000000018d252d94 -[__NSURLSessionWebSocketTask _onqueue_enableWebSocketFraming:] + 456 (LocalWebSocketTask.mm:221) 2 CFNetwork 0x000000018d251ed0 -[__NSURLSessionWebSocketTask _onqueue_didReceiveResponse:completion:] + 2096 (LocalWebSocketTask.mm:663) 3 CFNetwork 0x000000018d09ad04 __67-[__NSCFLocalSessionTask connection:didReceiveResponse:completion:]_block_invoke + 168 (LocalSessionTask.mm:1205) 4 CFNetwork 0x000000018d071ce4 -[__NSCFLocalSessionTask connection:didReceiveResponse:completion:] + 280 (LocalSessionTask.mm:1149) 5 CFNetwork 0x000000018d10c61c __59-[__NSCFURLLocalSessionConnection _sendResponseToDelegate:]_block_invoke + 96 (SessionConnection.mm:1005) 6 CFNetwork 0x000000018d10c5ac -[__NSCFURLLocalSessionConnection _sendResponseToDelegate:] + 120 (SessionConnection.mm:999) 7 CFNetwork 0x000000018d0738e8 -[__NSCFURLLocalSessionConnection _tick_sniffNow] + 284 (SessionConnection.mm:796) 8 CFNetwork 0x000000018d0778dc -[__NSCFURLLocalSessionConnection _tick] + 324 (SessionConnection.mm:812) 9 CFNetwork 0x000000018d072d0c -[__NSCFURLLocalSessionConnection _didFinishWithError:] + 236 (SessionConnection.mm:1190) 10 CFNetwork 0x000000018d10d9fc invocation function for block in SessionConnectionLoadable::withLoaderClientAsync(void (LoaderClientInterface*) block_pointer) + 28 (SessionConnection.mm:91) 11 libdispatch.dylib 0x000000018c6763e4 0x18c666000 + 66532 12 libdispatch.dylib 0x000000018c6c7298 0x18c666000 + 397976 13 libdispatch.dylib 0x000000018c66fa40 0x18c666000 + 39488 14 libdispatch.dylib 0x000000018c670548 0x18c666000 + 42312 15 libdispatch.dylib 0x000000018c679fac 0x18c666000 + 81836 16 libsystem_pthread.dylib 0x00000001d4edd5bc _pthread_wqthread + 272 (pthread.c:2437) 17 libsystem_pthread.dylib 0x00000001d4ee086c start_wqthread + 8 The full crash log is attached. 2021-07-14_01-57-44.4617_+0200-999b007c2d8c422ac2c0438fcfd94ecc55f99212.crash
Posted
by
Post not yet marked as solved
4 Replies
418 Views
I have some business requirements to send data to a particular cloud location while the app is not running (not even in the background). I am looking for Apple support on whether there are any services in iOS SDK which allow me to do the same. This service should continue to upload data until it detects that there is no more data left to be uploaded.
Posted
by
Post not yet marked as solved
5 Replies
690 Views
Crashed: com.apple.CFNetwork.Connection 0 libapple_nghttp2.dylib 0x1d29fa518 nghttp2_rcbuf_decref + 16 1 libapple_nghttp2.dylib 0x1d29f6b1c hd_context_free + 64 2 libapple_nghttp2.dylib 0x1d29fc7f0 nghttp2_session_del + 248 3 CFNetwork 0x188508dec _CFURLCachePersistMemoryToDiskNow + 6976 4 CFNetwork 0x1885094e0 _CFURLCachePersistMemoryToDiskNow + 8756 5 libdispatch.dylib 0x187a6da84 _dispatch_call_block_and_release + 32 6 libdispatch.dylib 0x187a6f81c _dispatch_client_callout + 20 7 libdispatch.dylib 0x187a77004 _dispatch_lane_serial_drain + 620 8 libdispatch.dylib 0x187a77c34 _dispatch_lane_invoke + 456 9 libdispatch.dylib 0x187a78ee8 _dispatch_workloop_invoke + 1680 10 libdispatch.dylib 0x187a824bc _dispatch_workloop_worker_thread + 764 11 libsystem_pthread.dylib 0x1d3af27a4 _pthread_wqthread + 276 12 libsystem_pthread.dylib 0x1d3af974c start_wqthread + 8 a lot of crash with this issue. just in iOS 14.
Posted
by