Skip to main content

Settings Crash

Comments

2 comments

  • Dan Dennison

    This crash is debilitating on macOS 27 Golden Gate.

    I am now effectively locked out of Accordance.

    The relevant stack frames:

    2  Foundation  -[NSCalendarDate initWithCoder:] + 0
    3  AppKit      -[NSControl _gestureRecognizerTrackingAction:forCell:withBounds:delegatingToCell:] + 1600
    4  AppKit      -[NSControl(_NSTracking) _gestureRecognizerTrackingAction:] + 468
    5  Foundation  __NSFireDelayedPerform + 376

    The Root Cause: A Dropped Legacy Cocoa Class

    1. -[NSCalendarDate initWithCoder:] has been purged or blocked: NSCalendarDate is an obsolete OpenStep/NeXT legacy date class that Apple formally deprecated years ago in favor of NSDate and NSCalendar. In modern macOS runtimes (macOS 15+ and your macOS 27 environment), unarchiving or instantiating NSCalendarDate via NSCoder / initWithCoder: throws an unhandled NSInvalidArgumentException or internal assertion failure immediately upon decode.
    2. Where the archive is coming from: When you click the UI control to trigger the rebuild (or open the tracking sheet), Accordance unarchives a legacy nib, cell configuration, or serialized state dictionary that contains an archived NSCalendarDate object or relies on a date-tracking cell metadata block.
    3. The result: The decoding fails inside initWithCoder:, raising an Objective-C exception caught by abort() on Thread 0.

    Because this is hardcoded into the compiled nib/binary structures, clicking that specific UI element will always crash the application on your current macOS version.

    Folks, can somebody please look at this?

    Mike Garrity  Richard Perry 

    2
  • Dan Dennison

    Closing the loop here, this appears to be fixed in 14.2.0b4

    http://accordancefiles1.com/products/Accordance14_Beta_installer.dmg

    0

Please sign in to leave a comment.

Powered by Zendesk