DriveVault 1.2.2 crashes on launch (macOS 14.7 / Intel Mac)
mg
Hi DriveVault Support Team,
I recently downloaded DriveVault (version 1.2.2, build 19) from the Mac App Store, but the application crashes immediately upon launch ("closes unexpectedly").
I am running macOS 14.7 (23H124) on an Intel-based MacBook Pro (MacBookPro16,1, Intel Core i7).
When launching the app via Terminal, it logs the following error right before crashing:
2026-06-25 15:33:50.806 DriveVault[72162:25421901] 📁 AppContainerManager - Using consistent sandbox path, no migration needed
2026-06-25 15:33:50.808 DriveVault[72162:25421908] 📁 AppContainerManager - Using sandbox path: /Users/[redacted]/Library/Containers/FullAccess.DriveVaultApp/Data/Library/Application Support/DriveVault
📂 FileMetadata: Loading from: /Users/[redacted]/Library/Containers/FullAccess.DriveVaultApp/Data/Library/Application Support/DriveVault/MetadataCache/FileMetadata.json
📂 FileMetadata: No existing metadata file found
2026-06-25 15:33:50.812 DriveVault[72162:25421901] 🔧 MenuBarManager: Checking if menu bar is allowed...
2026-06-25 15:33:50.812 DriveVault[72162:25421901] ✅ MenuBarManager: Enabling menu bar for production
2026-06-25 15:33:50.812 DriveVault[72162:25421901] 🔧 MenuBarManager: Setting up menu bar...
Assertion failed: (CGAtomicGet(&is_initialized)), function CGSConnectionByID, file CGSConnection.mm, line 419.
It appears to be an initialization issue related to the Menu Bar/NSStatusItem and the SkyLight framework on Intel architecture.
Here is the relevant excerpt from the macOS Crash Report (Thread 0):
Plaintext
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x7ff803d6fd96 __pthread_kill + 10
1 libsystem_pthread.dylib 0x7ff803da8ebd pthread_kill + 262
2 libsystem_c.dylib 0x7ff803ccea79 abort + 126
3 libsystem_c.dylib 0x7ff803ccdd68 __assert_rtn + 314
4 SkyLight 0x7ff8094851fc CGSConnectionByID + 415
5 SkyLight 0x7ff80970d759 SLSRegisterConnectionNotifyProc + 43
6 AppKit 0x7ff808081e22 +[NSCGSStatusItem addNavigationChangedNotificationHandler:] + 123
7 AppKit 0x7ff807dfc055 __53+[NSStatusItem _registerNotificationHandlersIfNeeded]_block_invoke + 36
8 libdispatch.dylib 0x7ff803c07dbc _dispatch_client_callout + 8
9 libdispatch.dylib 0x7ff803c0904e _dispatch_once_callout + 20
10 AppKit 0x7ff807dfcf2d -[NSStatusItem _initWithStatusBar:length:priority:systemInsertOrder:] + 94
11 AppKit 0x7ff807766fe1 -[NSStatusBar _statusItemWithLength:withPriority:] + 71
12 DriveVault 0x10368fb5a 0x10316b000 + 5393242
I have already tried clearing the application container directory (~/Library/Containers/FullAccess.DriveVaultApp), but the issue persists.
Could you please look into this and let me know if a fix will be available soon?
Thank you for your time and assistance.
Frase
Hey there, thanks so much for sharing the terminal report. Allowed us to patch this fix in 10 minutes. DriveVault was setting up its menu bar icon a split-second too early in launch, before macOS was ready. On silicon Macs this is fine, but Intel hardware exposed the timing bug and crashed the app. We've just swapped some timing around which should fix the issue. We'll ship this hopefully today / tomorrow!
mg
Frase Wonderful! Thank you so much!
Frase
mg shipped about an hour ago to Apple - so we're just waiting on their review. Please let us know if this fixed the issue.
Frase
mg: Heya! Just to let you know we successfully shipped the update on Friday, so you should be able to update now. Please do let us know if that has fixed your issue!
mg
Frase all good! Thank you so much! 🫶�
Frase
mg: Perfect! Glad to hear it! Enjoy DriveVault!!