Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

未關閉
#1,591 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
1-2 天
新手友好度
43/100
Issue 類型
文件
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
dart, flutter
領域
desktop, devops

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
Dart
星號
23
分支
1
平均合併
31 分鐘
30 天內合併 PR
570

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

QueryaHub/Querya-Desktop 的其他 Issue

查看 QueryaHub/Querya-Desktop 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。