π§ͺ macOS 27 (Developer Preview) β issues & how to collect debug info #21
ricardoleal
started this conversation in
General
Replies: 1 comment
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
TimeMachineTrimmer currently targets macOS 26 (Tahoe). macOS 27 is a pre-release and may introduce regressions in areas the app depends on: menu bar event dispatch, XPC/PrivilegedHelper communication, TCC/FDA enforcement, and
tmutilbehaviour.Use this discussion to report any issues found on macOS 27. Please collect the info below before posting β it cuts investigation time significantly.
1. Environment
27.0 (26A5XXX).dmg/ Homebrew tapQuick version check:
2. Runtime logs
Run this before reproducing the issue, then paste the output:
The filter covers both the main app and the PrivilegedHelper, which handles the actual
tmutiloperations.3. PrivilegedHelper status
The app uses a privileged helper tool (
com.ricardoleal.TimeMachineTrimmer.Helper) registered with launchd via SMJobBless. If this isn't running, nothing works.Check whether it's installed and running:
Check for its LaunchDaemon plist:
If found, read its content:
Check whether the helper binary is installed:
4. App bundle Info.plist
Share the full content of the app's Info.plist β useful to verify entitlements and bundle identifiers are intact after install:
And for the PrivilegedHelper embedded plist (if accessible):
5. Full Disk Access (FDA)
The app requires FDA to read
/Library/Preferences/com.apple.TimeMachine.plistand list backups. Without it, operations silently fail.Check whether the app appears in Privacy & Security:
Look for
com.ricardoleal.TimeMachineTrimmerandcom.ricardoleal.TimeMachineTrimmer.Helperin the output.Also confirm whether the system TimeMachine plist is readable at all:
If FDA is stuck or was never prompted, reset and re-grant:
6. App preferences plist
If the file doesn't exist, mention it β it means the app never successfully wrote its defaults.
7. Crash reports
Open the most recent
.ipsor.crashfile and paste the first 60 lines. Also check Console.app β Crash Reports.8. tmutil sanity check
Confirms whether the issue is at the app layer or the system layer:
Issue report template
All reactions