Post not yet marked as solved
Hi! My app is showing a rare crashes that I am not able to reproduce. The stack trace starts with lines like the following:
0 MyApp 0x00000001028edf38 function signature specialization <Arg[0] = Dead> of MyApp.CollectionViewDataSource.collectionView(_: __C.UICollectionView, didSelectItemAt: Foundation.IndexPath) -> () (<compiler-generated>:0)
1 MyApp 0x00000001028ed258 @objc MyApp.CollectionViewDataSource.collectionView(_: __C.UICollectionView, didSelectItemAt: Foundation.IndexPath) -> () (<compiler-generated>:0)
2 UIKitCore 0x00000001a4fd806c -[UICollectionView _selectItemAtIndexPath:animated:scrollPosition:notifyDelegate:deselectPrevious:performCustomSelectionAction:] + 1020
3 UIKitCore 0x00000001a536effc -[UICollectionView touchesEnded:withEvent:] + 612
…
What does Arg[0] = Dead actually mean and what could I do to avoid this crash?
Post not yet marked as solved
Hi!
I‘ve used my old iPad Pro as my iOS 15 beta test device. With one of the latest beta releases the device showed the behavior that it never completed the „Verifying update“ step.
With the official release of iOS 15 I used a desktop connection to restore the device to the official iOS 15 release.
However, the 15.0.2 release of today is again stuck in the „Verifying update“ step.
What could be the problem here? I thought restoring the device will reset the device to factory settings? Other iOS devices on my network update without my issues. It‘s just this beta test device that‘s making problems.
Christian
Post not yet marked as solved
Hi!When trying to watch the log from my Apple Watch in Console.app, I get a warning icon next to the device icon and no log entries appear in the log pane.In my macOS log I can see the following error message from Console.app:AMDeviceStartSession (thread 0x70000e748000): Could not start session with PROXIED device d5a81d6c286369a418d83c454fe1fef8b8258402: kAMDTimeOutErrorOnce in a while Console.app shows an error allert with the title "The user has not responded to the pairing request on '***' Respond to the Trust prompt on the device.".But on the watch no pairing request shows up …Any idea on how to get access to my watchOS logs?RegardsChristian
Post not yet marked as solved
Hi!I use DNSServiceQueryRecord on macOS and iOS for querying the current name server for specific records.guard DNSServiceCreateConnection(result.serviceRef) == kDNSServiceErr_NoError,
DNSServiceQueryRecord(result.serviceRef,
DNSServiceFlags(kDNSServiceFlagsValidate | kDNSServiceFlagsTimeout),
DNSServiceInterface(kDNSServiceInterfaceIndexAny),
self.tlsaLookupName,
DNSServiceType(DnssdTLSAResolver.kDNSServiceType_TLSA),
DNSServiceClass(kDNSServiceClass_IN),
self.callback, &result) == kDNSServiceErr_NoError,
DNSServiceSetDispatchQueue(result.serviceRef.pointee, self.dnssdResolveQueue) == kDNSServiceErr_NoError,
DNSServiceProcessResult(result.serviceRef.pointee) == kDNSServiceErr_NoError
else { return }And I can see the following strange error messages on the log from time to time:dnssd_clientstub DNSServiceProcessResult daemon version 3 does not match client version 1And the other message is:dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply functionWhat is happening here? Has anybody else seen these messages?RegardsChristian
Hi there,I'm currently working on the network part of my appliation where I require a DNS response being validated using DNSSEC. I use DNSServiceQueryRecord for the query and kDNSServiceFlagsValidate as a flag parameter.However, I want to query for DNSServiceType 52, a type which isn't defined in the header.The callback is called correctly, but the validation result does always contain: kDNSServiceFlagsBogus.The documentation says:If the response cannot be verified to be secure due to expired signatures, missing signatures, and so on, then the results are considered to be bogus.How can I find out more information about the error (RFC 4033 has some information for the "bogus" response)? How should I treat the 'bogus' response? The dnssd API describes the following four result codes:kDNSServiceFlagsSecure - The response has been validated by verifying all the signature …kDNSServiceFlagsInsecure - A chain of trust cannot be built …kDNSServiceFlagsBogus - If the response cannot be verified to be secure due …kDNSServiceFlagsIndeterminate - There is no valid trust anchor that can be used …Regards,Christian
Post not yet marked as solved
HI!I've got an watchOS app that I would like to test. But when trying to install it from an iOS 11 device and a watchOS 4 first generation watch, I get the following error:The screenshot says: "Couldn't install *** on Apple Watch. Try again. [OK]". I found the following message in the log file:… TestFlight(WatchKit)[15032] : -[SPDeviceConnection installApplication:withProvisioningProfiles:onPairedDevice:completion:]_block_invoke:426: installApplication for de.***.watchkitapp, withProfiles, failed with: Error Domain=ACXErrorDomain Code=19 "No WatchKit app is installed with the identifier de.***.watchkitapp" UserInfo={SourceFileLine=509, NSLocalizedDescription=No WatchKit app is installed with the identifier de.***.watchkitapp, FunctionName=-[ACXDeviceConnectionClient installApplication:withProvisioningProfileInfo:forTestFlight:onDeviceWithPairingID:completion:]}It's working fine on a second generation watch running the same software configuration or a first gen watch running watchOS 3.ThanksChristian
cmittendorf.