Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

docs(macos): sandboxed vs non-sandboxed builds and the minimum macOS version

Closed
  • Is something wrong?
#1,591 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
43/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter
Domain
desktop, devops

Research direction

Read docs/macos-signing.md, the README and contributor docs, then check the Xcode project’s Release.entitlements and MACOSX_DEPLOYMENT_TARGET settings. Determine how the sandboxed and signed builds differ and check the plugins’ macOS requirements. Done means the unsigned build behavior and limitations are documented or its sandbox choice is resolved, and the documented minimum macOS version matches the supported configuration.

Written by the indexing model from the issue text.

Description

documentation P3

Problem

The shipped macOS app is one of two different programs depending on CI secrets:

  • Signed builds use ReleaseSigned.entitlements: no App Sandbox, hardened runtime.
  • Without MACOS_* secrets (forks, local flutter build macos) the Xcode project's Release.entitlements applies: App Sandbox on, only network.client/server and files.user-selected.read-write.

In the sandboxed build ~/.querya, extension processes (sandbox-exec inside a sandbox), in-place updates into /Applications, the MCP socket and previously chosen SQLite file paths (no security-scoped bookmarks) do not behave like the signed build. docs/macos-signing.md mentions it; README and the contributor docs do not.

Also MACOSX_DEPLOYMENT_TARGET = 10.15 in all configurations while the docs target macOS 14+ for ProMotion; the minimum is not checked against the plugins' requirements.

Tasks

  • Decide: ship the unsigned build without the sandbox too, or document the limitations in README / CONTRIBUTING.
  • Align and document the minimum macOS version.
Dominant language
Dart
Stars
23
Forks
1
Avg merge
49m
Merged PRs (30d)
496

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QueryaHub/Querya-Desktop

All issues in QueryaHub/Querya-Desktop

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.