SUMMARY:
Window snapping only works once per macOS Space, then fails until switching to a different Space.
SYSTEM INFORMATION:
- macOS Version: macOS 26.2 (Tahoe)
- Mac Model: MacBook Pro (M1, 2020) - MacBookPro17,1
- RAM: 16 GB
- BTT Version: 6.069 (build 2026011807)
- Display: External SAMSUNG display, 1920x1080, connected to M1 MacBook Pro
- Display ID: 1625, Vendor: 19501
DETAILED BEHAVIOR:
- Window snapping works only ONCE per Space
- Subsequent attempts to snap any window on the same Space fail (no snapping occurs)
- Switching to a different Space allows ONE snap there
- Switching back to the original Space allows ONE more snap again
- Pattern repeats indefinitely: one snap per Space per navigation to it
- Snap area preview (colored borders) DOES appear when snap succeeds, but only then
- Toggling "Enable Window Snapping" off and back on allows for one more snap in present space
TROUBLESHOOTING STEPS ATTEMPTED:
- ✓ Verified BTT has Accessibility permissions
- ✓ Restarted BTT multiple times
- ✓ Checked and confirmed window snapping is enabled in BTT preferences
- ✓ Disabled all macOS native window tiling features
- ✓ Confirmed no other window management apps are installed
- ✓ Reset snap areas multiple times (most likely irrelevant)
- ✓ Toggled BSTSequoiaUseClassicSnapping (both true and false)
- ✓ Disabled BSTLeftHalfBlock and BSTRightHalfBlock
- ✓ Complete clean reinstall of BTT (removed app + all support files)
- ✓ Tested in Safe Mode (issue persists)
- ✓ Run terminal command: sudo tccutil reset Accessibility
- ✓ Installed BetterSnapTool and run it alongside as a test which works
DATABASE ANALYSIS FINDINGS:
-
BSTDragPoint entities (snap areas) are NOT being created in the database
- Query: SELECT COUNT(*) FROM ZBTTBASEENTITY WHERE Z_ENT = 5;
- Result: 0 (should have multiple snap area definitions)
-
Display recognition issue initially found and fixed:
- Display entry (Z_ENT = 4, Z_PK = 18812) had empty ZNAME field
- Manually set ZNAME = 'SAMSUNG' to match system display name
- This improved display recognition but did not fix snapping issue
-
Log analysis shows:
- "Did reset snap areas 0 0" (should create default snap areas, not 0)
- "SNAPAREA|return existing (updated)" followed by "0 dragpoints: 0 - 0"
- Display is now recognized but no snap areas are being created/persisted
RELEVANT LOG ENTRIES:
2026/01/19 06:42:49:186|SNAPAREA|return existing (updated)|
2026/01/19 06:42:49:186|SNAP|Did recognize 1625 0 dragpoints: 0 - 0|
2026/01/19 06:30:45:657|SNAP|Did reset snap areas 0 0|
Note: When dragging windows, NO snap-related log entries appear.
CURRENT BTT PREFERENCES (Relevant Settings):
BSTAllowInsideDragSnap = 1
BSTDontShowSnapAreasWhileModMoving = 0
BSTIncreaseSnappingArea = 1
BSTSequoiaUseClassicSnapping = 1 (tested with both 0 and 1)
BTTWindowSnappingHighPerformanceMode = 1
BTTWindowSnappingHapticFeedback = 0
cornerSnap = 1
snapBottomLeft = 1
snapBottomRight = 1
snapTopLeft = 1
snapTopRight = 1
BSTLeftHalfBlock = 0 (set to false during troubleshooting)
BSTRightHalfBlock = 0 (set to false during troubleshooting)
DATABASE STRUCTURE:
- Main database: btt_data_store.version_6_069_build_2026011807
- Display entry exists: Z_PK = 18812, ZDISPLAYID = 2, ZMODEL = 1625, ZVENDOR = 19501
- Display name now set: ZNAME = 'SAMSUNG'
- Snap areas (BSTDragPoint, Z_ENT = 5): COUNT = 0 (PROBLEM)
HYPOTHESIS:
The "once per Space" pattern suggests BTT is:
- Tracking which windows have been snapped on which Spaces
- Failing to clear or reset this tracking state properly
- Only allowing one snap operation before marking the window as "already snapped" for that Space
- The lack of persistent snap area definitions in database suggests the reset function is broken
This appears to be a regression introduced for macOS Sequoia/later versions, possibly related to:
- Changes in window management APIs in macOS 26.x
- The BSTSequoiaUseClassicSnapping toggle behavior
- Display recognition changes for external monitors on Apple Silicon Macs
REQUESTED ACTION:
Please investigate the snap area creation/persistence mechanism and the "once per Space" limitation. The issue reproduces consistently on a clean BTT installation with default settings on macOS 26.2.
CONTACT INFORMATION:
FILES AVAILABLE FOR DEBUGGING:
- Complete BTT database backup available
- Full BTT logs available
- System profiler output available
- Can provide additional diagnostic information as needed