It dawned on me that it was probably getting bad data from the network. My friend (who works on iTunes servers) fixed it on the server side, and that's why the problem went away (although hopefully they update the client code to be more robust. I bet if this were written in Swift, this particular error wouldn't have happened).
> On Dec 3, 2017, at 19:41 , Richard Charles <rcharles...@gmail.com> wrote: > > >> On Dec 3, 2017, at 8:16 PM, Jerome Krinock <je...@ieee.org> wrote: >> >>> On 2017 Dec 1, at 21:54, Rick Mann <rm...@latencyzero.com> wrote: >>> >>> Certificate Key (CK) >> >> The stack trace in your first post indicates that CK is more likely >> CommerceKit. For example: >> >>> On 2017 Dec 1, at 21:15, Rick Mann <rm...@latencyzero.com> wrote: >>> >>> 5 CommerceKit 0x00007fff5a62d858 -[CKStoreDAAPLibrary >>> _writePersistedStore] + 402 > > > CommerceKit trying to write out some sort of iTunes Digital Audio Access > Protocol (DAAP) file. > > --Richard Charles > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/rmann%40latencyzero.com > > This email sent to rm...@latencyzero.com -- Rick Mann rm...@latencyzero.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
