Crash on macOS Tahoe 26.5

[bertofa]

Since updating to macOS Tahoe 26.5, Latest crashes on launch and displays the following exception.

Latest version: 0.11 (1306).

Nome eccezione: NSGenericException
Descrizione: Unable to activate constraint with anchors <NSLayoutXAxisAnchor:0x743c96bc0 "Latest.UpdateGroupCellView:0x743e04900.left"> and <NSLayoutXAxisAnchor:0x743c96c80 "Latest.UpdateGroupRowView:0x743e04600.left"> because they have no common ancestor. Does the constraint or its anchors reference items in different view hierarchies? That's illegal.
Informazioni utente: (null)

0 CoreFoundation 0x0000000184e4d1c0 __exceptionPreprocess + 176
1 libobjc.A.dylib 0x00000001848d691c objc_exception_throw + 88
2 CoreAutoLayout 0x000000018f5ccc78 -[NSLayoutConstraint setActive:] + 0
3 AppKit 0x0000000189446194 -[NSTableRowData _updateConstraintsAtColumn:row:rowView:] + 324
4 AppKit 0x0000000189445fb8 -[NSTableRowData _updateConstraintsForRowView:atRow:] + 64
5 AppKit 0x000000018948f3b8 -[NSTableRowData updateColumnWidthsForRowView:atRow:] + 184
6 AppKit 0x00000001892a42b4 -[NSTableRowData _commonUpdateFramesAndRemoveForRowView:row:] + 56
7 AppKit 0x00000001892a28e8 -[NSTableRowData _updateVisibleViewsBasedOnUpdateItems] + 3380
8 AppKit 0x000000018928b250 -[NSTableRowData endUpdates] + 352
9 AppKit 0x000000018928b0ac -[NSTableView _endUpdateWithTile:] + 108
10 AppKit 0x000000018933cdb4 -[NSTableView endUpdates] + 28
11 Latest 0x0000000104f621dc Latest + 123356
12 Latest 0x0000000104f5df70 Latest + 106352
13 Latest 0x0000000104f5dff0 Latest + 106480
14 Foundation 0x000000018664703c __NSFireDelayedPerform + 372
15 CoreFoundation 0x0000000184df8318 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 32
16 CoreFoundation 0x0000000184df8010 __CFRunLoopDoTimer + 980
17 CoreFoundation 0x0000000184df7b88 __CFRunLoopDoTimers + 280
18 CoreFoundation 0x0000000184dddc38 __CFRunLoopRun + 1816
19 CoreFoundation 0x0000000184eb01c4 _CFRunLoopRunSpecificWithOptions + 532
20 HIToolbox 0x0000000191bc3560 RunCurrentEventLoopInMode + 320
21 HIToolbox 0x0000000191bc68bc ReceiveNextEventCommon + 488
22 HIToolbox 0x0000000191d5014c _BlockUntilNextEventMatchingListInMode + 48
23 AppKit 0x00000001898b835c _DPSBlockUntilNextEventMatchingListInMode + 228
24 AppKit 0x000000018920c084 _DPSNextEvent + 576
25 AppKit 0x0000000189da18b0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
26 AppKit 0x0000000189da15bc -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
27 AppKit 0x00000001891ff13c -[NSApplication run] + 368
28 AppKit 0x00000001891d77b0 NSApplicationMain + 880
29 Latest 0x0000000104f64df0 Latest + 134640
30 dyld 0x0000000184963e00 start + 6992

[SteveDavidson]

I'm seeing something similar. Tried it for the first time, and while updating Locations in the settings it crashed and never recovered. I attempted to delete the .plist file in ~/Library/Preferences, but that didn't help. Removed that file and replaced the application with a fresh copy (in an attempt to start clean), but that didn't work. I can get it to run in another user account (which suggests that my "start clean" didn't work).

I think the trigger for the initial crash was that I added a folder to the "Check apps from:" window that isn't readable from that account (I typically run as a Standard user, do maintenance from an Admin account, and what I was adding was /Users/standard-user-name/Applications folder). But deleting com.max-langer.Latest.plist should have cleared that out (just removing the added location should have fixed that too, but it didn't). So there must be some other file that is present that it uses (and is causing it to trip up).

I'm quite convinced that attempting to access a folder without permission was the trigger for the unrecoverable crash.

I hope this information is useful. I'd like to try your application from my Admin account.

Thank you

[SteveDavidson]

An update on my comment: Signing out of the Admin account and returning later, I discovered that the “clean start” would work. It appears that a cache was the thing that prevented the clean start. And I’ll avoid adding any un-readable directories to Settings/Locations.