Describe the bug
BetterSnapTool has worked reliably for several years, but window snapping has recently stopped working completely.
When dragging windows around the screen, the snap areas no longer appear, and windows do not snap into position.
I have not recently updated macOS (currently running Sequoia 15.6.1). I suspect the issue may be related to the recent BetterSnapTool update to version 1.10.1, released on 9 October 2026.
Troubleshooting already performed:
- Restarted my Mac.
- Uninstalled BetterSnapTool, including manually deleting its two associated Library folders.
- Reinstalled BetterSnapTool from the App Store.
- Checked the relevant macOS permissions:
- Open at Login: BetterSnapTool is listed.
- Allow in Background: No BetterSnapTool entry is present.
- Accessibility: BetterSnapTool is listed with permission enabled.
- Removed BetterSnapTool from the Accessibility permissions list, relaunched the application and granted permission again when prompted. The permission was successfully restored, but window snapping still does not work.
Despite these steps, the problem persists.
The application does not crash or display any error messages. Window snapping simply no longer works areas are not displayed.
Affected input device
Apple Magic Mouse and Apple Keyboard, connected to a Mac mini M2 Pro.
Screenshots
Screenshot attached showing BetterSnapTool listed under macOS Accessibility settings with permission enabled.
Device information
Type of Mac: Mac mini M2 Pro
macOS version: Sequoia 15.6.1
BetterSnapTool version: 1.10.1 (App Store update dated 9 October 2026)
Additional information
The issue appears to have started following the latest BetterSnapTool update, although I cannot confirm that the update is responsible.
BetterSnapTool previously worked reliably on this Mac, and I have not made any recent changes to macOS.
There are no crashes or error messages, and the issue persists after a complete reinstall, removal of the application's Library folders, restarting macOS and resetting Accessibility permissions.
Could you confirm whether this is a known issue with version 1.10.1 or a possible regression introduced by the latest update?
I would appreciate any further troubleshooting suggestions or a potential fix.
