Sent from my iPhone
> On 27 Mar 2017, at 23:37, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Mar 26, 2017, at 10:04 PM, Gerriet M. Denkmann <gerri...@icloud.com> >> wrote: >> >> Yes, you are right. And I have to apologise for not spotting this: >> >> *** Terminating app due to uncaught exception 'NSInvalidArgumentException', >> reason: '*** setObjectForKey: object cannot be nil (key: SortedKeys.plist)' > > I recommend always having an exception breakpoint set, to catch things like > this. This same error occurred twice within 250 days. Running the code for about a year in Xcode is really not feasible. > >> I suspect that this might be a rare timing issue, i.e. SortedKeys.plist has >> not been fully written when serializedRepresentation is called. > > Is the snippet you posted all code running in the same thread/queue? If so, > there couldn’t be a race condition between writing the plist and reading it. Yes, all is running in the same thread. If no race condition (and I agree that there should be none) what else could be causing this? Kind regards, Gerriet _______________________________________________ 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
