[ISSUE-495]: Fix access data permission prompt and Core Data crash during setup#500
Merged
ptsochantaris merged 2 commits intoptsochantaris:mainfrom Aug 23, 2025
Conversation
ptsochantaris
approved these changes
Aug 23, 2025
Owner
ptsochantaris
left a comment
There was a problem hiding this comment.
Thanks so much for this! That permission requirement was extremely well hidden, as a Trailer user I'm definitely grateful for not having that noise anymore.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #495
Primary Fix: Access Data Permission Prompt
The "access data" permission prompt was appearing because:
Without proper
NSAppleEventsUsageDescriptionentries, the system shows a generic "access data" prompt.These changes provide clear, user-friendly explanations for why the app needs Apple Events access, replacing the confusing generic permission prompt with proper context.
The launcher also needs
com.apple.security.automation.apple-eventsentitlement for automation permissionsSecondary Fix: Core Data Crash in SetupAssistant
While testing the permission fix, discovered and fixed a crash in
SetupAssistant.swiftthat occurred during server setup:The app crashed with
assert(!objectID.isTemporaryID)when trying to set auth tokens on newly created ApiServer objects.Solution:
Ensures the server has a permanent Core Data object ID before setting the auth token, preventing the assertion failure.
Test
Started from Trailer 1.8.14 (current main a9d2353) on Mac Sequoia 15.6