fix(desktop): first-launch resilience - #27
Merged
Conversation
- Raise the sidecar boot deadline from 30s to 90s: on the first launch Gatekeeper verifies the whole ~400MB bundle, which can exceed 30s on slower machines and produced a spurious 'server did not start' dialog - Update the splash after 15s to explain that the first launch takes longer while macOS verifies the app - Include the recent sidecar log tail in the startup-failure dialog so error reports are actionable - Log when a second instance defers to the one already running
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
1 participant
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.
Summary
Why
Follow-up hardening from real-world testing of the v0.4.0 DMG install flow (quarantined download → /Applications → first launch).
Testing