Report Bugs

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.

I click between hard drives then the app lags and crashes

I go to purchase a tier upgrade (happens on any one) and the app store pop-up doesn't have a confirm option

There are potentially some opportunities for performance enhancement: I have 19 drives scanned, with ~27Tb of data. App startup takes several minutes while the indexes are loaded on an M2 Max. Optimising this would of course be very useful, but there are ways to make it less problematic. Once the drive list has been populated, you could remove the modal and report the index loading as a non-blocking status element (locking out the appropriate UI elements for search/drive interaction etc until the indexes are fully loaded). This could then potentially allow unrelated operations to take place (adding new drives, for example) without having to wait for the indexes to load. Also, there are lots of instances when backend processing makes the UI unresponsive or affects the speed of animations. It could be worth looking at thread priorities etc to ensure that backend operations don't affect the performance of the UI.

Not entirely certain whether this counts as a bug or a feature request, but: particularly when scanning hard drives, the 'cataloging files' step of the drive scan takes a long time and offers no onscreen feedback to show that it's working. This makes it difficult to know whether the app/process has failed or crashed, or whether it's just creating a large initial list. It would be very helpful to show some form of progress during this step -- perhaps a 'objects added to catalog' number that could be updated every few seconds to show activity and/or an optional 'details' output (perhaps a UI accordion-like element that can be expanded) to show file-by-file or folder-by-folder progress during the cataloging step . Once the catalog is built, the UI does a good job of indicating the preview-building progress, and I understand that a % complete figure isn't possible during the catalog step, but I suspect you may lose some potential users when people start a scan, and then see no obvious progress for several minutes...

I scanned a local SSD using quick scan and it took about 30seconds however when I scan using the full scan it always gets stuck generating previews.

When it starts to scan the screen is unreadable.

Even though the skip all bundle types is checked, it still scan Eagle .library files

I cannot select the unlimited plan. Scroll in the purchase window does not work. Max available tier is 20.