forked from mirkofetter/ScreenSaverMinimal
-
Notifications
You must be signed in to change notification settings - Fork 7
Issues With macOS Tahoe beta
Guillaume Louel edited this page Jul 28, 2025
·
1 revision
Last updated: July 28, 2025
This document tracks known issues with screen savers on macOS 26 (Tahoe) based on community reports and testing.
- Issue: Screen Saver pane removed from System Settings, now in a modal dialog within Wallpaper settings
- Impact: Smaller, non-resizable preview window, less convenient access
- Workaround: None - UI change is intentional
- Status: Permanent change ? Reported to Apple as FB18698083
- Issue: System Settings launches two legacyScreensaver instances simultaneously (legacyScreenSaver (Wallpaper) and (Wallpaper (System Settings)))
-
Details:
- One fullscreen instance on main monitor
- Second instance with
isPreview=truebut frame0,0,0,0
- Impact: Rendering conflicts, preview issues
- Workaround: None identified
- Status: Reported to Apple as FB18697726
- Issue: Screen savers invisible or non-functional on secondary monitors
- Details: Not 100%, may happen more with 2 different screen savers set on different monitors. May counteract previously existing attempts to fix previous multimonitor bugs.
- Impact: Blank screens on secondary displays
- Workaround: None identified
- Status: Under investigation
- Issue: Screen saver instances don't properly exit, causing instance stacking
-
Details: Previous
exit(0)workarounds no longer effective - Impact: Resource waste, unpredictable behavior
-
Workaround: Force quit
legacyScreenSaver (Wallpaper)process - Status: Workaround implemented in this template by delaying
-
Issue:
isPreviewdetection broken, opposite behavior from previous versions - Details: Framework provides incorrect preview state
- Impact: Cannot reliably determine preview vs fullscreen mode
- Workaround: Frame size detection (unreliable)
- Status: No reliable workaround available
- Issue: Existing workarounds from previous macOS versions no longer work
- Impact: Developers must find new solutions for each Tahoe-specific bug
- Status: Ongoing adaptation required
-
Issue: Multiple
startAnimation()calls without correspondingstopAnimation() - Details: Framework may call start multiple times, leading to resource leaks
- Impact: Timer leaks, unpredictable behavior
- Workaround: State tracking implemented in this template
- Status: Defensive programming approach adopted
This ScreenSaverMinimal template includes several adaptations for Tahoe issues:
- Instance Tracking: Comprehensive logging to identify multi-instance scenarios
- Animation State Management: Prevents multiple timer creation from duplicate start calls
- Process Identification: Logs help distinguish between different hosting processes
- Exit Fix: Implements timed exit for the broken restart mechanism
- Primary discussion thread
- Apple Feedback: FB18697726
- Previous Ventura issues