Posts

Post not yet marked as solved
3 Replies
482 Views
I'm seeing crashes within NWPathMonitor.pathUpdateHandler and in various parts of NWPath (sometimes on dealloc of NWPath). One thing I noticed is that we are using a global concurrent queue in the call to NWPathMonitor.start(queue:). Could this be the reason? The crash isn't easily reproducible, but I'll see if I can find a way to test this. It would be nice to have an authoritative answer about this, though. The documentation makes no mention that the queue must be serial. And NWPath is a struct, so it seems unexpected to require a serial queue. To be clear, I'm doing something like this: let nwPathMonitor = NWPathMonitor() nwPathMonitor.pathUpdateHandler = { [weak self] path in guard let self else { return } // do stuff with path } nwPathMonitor.start(queue: DispatchQueue.global(qos: .background))
Posted
by danny_int.
Last updated
.
Post not yet marked as solved
3 Replies
333 Views
I've noticed that our apps get these errors with some regular occurrence: Error Domain=NSURLErrorDomain Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made. I suspect the issue may be because of misconfigured VPNs. But is there any way to get more details about the cause of these SSL failures? If it's an issue with certificate validation or something, it would be great to get the certificate seen at the time of the error as sometimes a simple retry ends up working. I'm not doing anything particularly special network-wise... using standard URLSession with the default configuration. I have tried implementing URLSessionDelegate.urlSession(:didBecomeInvalidWithError:) and URLSessionDelegate.urlSession(:didReceive:completionHandler:) to see if I could get more details, but nothing.
Posted
by danny_int.
Last updated
.
Post not yet marked as solved
2 Replies
703 Views
When running xcodebuild on the command-line, I see many errors/warnings of the form: 2022-04-25 14:06:49.346 xcodebuild[49487:2429539] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7fb9fdc04d20), My iPhone 11, iPhone, 13.4.1 (17E262), 00008030-001570660282802E>: downgrading native architecture from arm64e to arm64 for com.apple.platform.iphoneos:13.4.1 This is for a device I no longer use or have. Where does this error come from and how can I get rid of it? I don't see it in Xcode's "Devices" list. And I see the same error repeated about 15 times (exact same device, version, etc.).
Posted
by danny_int.
Last updated
.
Post not yet marked as solved
0 Replies
368 Views
I'd like to distribute enterprise .IPA's to other members of our organization. We have a website that sits behind a VPN and requires SSO authentication. Is it possible to distribute IPA's like this? From my testing, it does not appear to be the case. But perhaps I'm missing something. I've tried putting both the manifest .plist and the .IPA on this website and it does not work. Moving the manifest off-site at least gives a prompt to install, but the install never completes. Only when both the IPA and manifest are off-site, does this seem to work. My guess is that whatever is handling the itms-services protocol on the phone must not be inheriting the permissions/auth info/cookies from the existing user session. If so, any chance this feature could be added?
Posted
by danny_int.
Last updated
.