> On May 10, 2016, at 5:16 PM, Roland King <r...@rols.org> wrote:
>
>>
>> 2016-05-10 16:58:36.066 iApp[2549:2131821] *** Terminating app due to
>> uncaught exception 'NSInternalInconsistencyException', reason: '(
>> "<UITextTapRecognizer: 0x175bb470; state = Possible; delaysTouchesEnded =
>> NO; view = <UITextField 0x175b3410>; target= <(action=oneFingerDoubleTap:,
>> target=<UITextInteractionAssistant 0x175bb3f0>)>; numberOfTapsRequired = 2>",
>> "<UITapAndAHalfRecognizer: 0x175bb810; state = Possible; view =
>> <UITextField 0x175b3410>; target= <(action=tapAndAHalf:,
>> target=<UITextInteractionAssistant 0x175bb3f0>)>>",
>> "<UITextTapRecognizer: 0x176c9d90; state = Possible; delaysTouchesEnded =
>> NO; view = <UITextField 0x175b3410>; target= <(action=oneFingerTap:,
>> target=<UITextInteractionAssistant 0x175bb3f0>)>>",
>> "<UIVariableDelayLoupeGesture: 0x175bbce0; state = Possible;
>> delaysTouchesEnded = NO; view = <UITextField 0x175b3410>; target=
>> <(action=loupeGesture:, target=<UITextInteractionAssistant 0x175bb3f0>)>>"
>> ): An -observeValueForKeyPath:ofObject:change:context: message was received
>> but not handled.
>> Key path: operations
>> Observed object: <NSOperationQueue: 0x175464f0>{name = 'Upload Queue'}
>> Change: {
>> kind = 1;
>> }
>> Context: 0x1c7bb0'
>> *** First throw call stack:
>> (0x20d19b8b 0x204d6dff 0x20d19ad1 0x2151cd7d 0x214a3d81 0x21482fe3
>> 0x21482c3b 0x2151e311 0x214822d1 0x2152f761 0xf89b5 0x25322521 0x253224b1
>> 0x2530a3eb 0x25321dd1 0x25321a3f 0x2531a3c7 0x252eac85 0x252e9229 0x20cdba67
>> 0x20cdb657 0x20cd99bf 0x20c28289 0x20c2807d 0x22244af9 0x253532c5 0x1146c7
>> 0x208d4873)
>> libc++abi.dylib: terminating with uncaught exception of type NSException
>>
>> BTW, if I remove the addObserver code, this doesn't happen.
>> -Carl
>
> Rather hard to tell but that seems to be hinting that the object not handling
> the KVO is a UITextTapRecognizer. But that may just be an artefact of what’s
> getting printed out.
>
> But I’ll ask the question I asked earlier
>
> "Are you getting the warning anywhere in your debug logs that an object was
> deallocated whilst still having KVO notifications registered on it? That
> explicitly tells you that the KVO notifications can get attached to the wrong
> object.”.
>
> because it looks here as if something was deallocated with KVO still attached
> to it and now your KVO calls are going somewhere incorrect.
Yes, I think it's because I didn't remove the observation when segueing to
another VC.
-Carl
_______________________________________________
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
