diff --git a/README.md b/README.md index 9064ddd..6825331 100644 --- a/README.md +++ b/README.md @@ -375,7 +375,7 @@ PATH="$HOME/.rustup/toolchains/stable-aarch64-apple-darwin/bin:$PATH" \ The result is one universal Mach-O including universal drag, PDF-render and doc-render sidecars. To produce the Windows installers and portable ZIPs — x64 and ARM64, both — from macOS, run `scripts/build-windows-release.sh`; full details are in `docs/BUILD_WINDOWS.md`. -**Permissions (macOS).** Screen Recording for capture, Files & Folders for the output folders you choose, Microphone when recording with audio. Shift checks Screen Recording before opening the overlay, so a denial surfaces an actionable error rather than a black screenshot. Dev builds signed with a local certificate keep those grants stable across rebuilds; distribution needs Developer ID plus notarization. +**Permissions (macOS).** Screen Recording for capture, Files & Folders for the output folders you choose, Microphone when recording with audio, and Local Network for **Send to a device**. Shift checks Screen Recording before opening the overlay, so a denial surfaces an actionable error rather than a black screenshot. A denied Local Network grant is quieter: Shift still sends its beacons and still answers anyone who addresses it directly, but it receives no group traffic, so the device list simply stays empty. Ad-hoc signed builds get a new code identity on every rebuild and macOS keys these grants to that identity, so an upgrade can ask again; distribution with Developer ID keeps them stable. ## Architecture diff --git a/README.zh-CN.md b/README.zh-CN.md index f4958ce..b4b2f5a 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -372,7 +372,7 @@ PATH="$HOME/.rustup/toolchains/stable-aarch64-apple-darwin/bin:$PATH" \ 产物是单个通用 Mach-O,内含通用版的拖拽、PDF 渲染与文档渲染伴生进程。若要在 macOS 上生成 Windows 安装版与便携版(x64 与 ARM64 两种架构都会产出),运行 `scripts/build-windows-release.sh`;完整步骤见 `docs/BUILD_WINDOWS.md`。 -**权限(macOS)。** 截图与录屏需要「屏幕录制」,输出目录需要「文件与文件夹」授权,带声音录屏需要「麦克风」。Shift 会在打开截图遮罩前先检查屏幕录制权限,因此被拒绝时给出的是可操作的提示,而不是一张全黑的截图。使用本地证书签名的开发构建,可以在反复重编译后保持这些授权稳定;对外分发则需要 Developer ID 证书与公证。 +**权限(macOS)。** 截图与录屏需要「屏幕录制」,输出目录需要「文件与文件夹」授权,带声音录屏需要「麦克风」,「发送到设备」需要「本地网络」。Shift 会在打开截图遮罩前先检查屏幕录制权限,因此被拒绝时给出的是可操作的提示,而不是一张全黑的截图。「本地网络」被拒绝时比较安静:Shift 仍会发出广播、也能回应主动找它的实例,但收不到组播,设备列表于是始终为空。ad-hoc 签名每次重新构建都会得到新的代码身份,而 macOS 正是按这个身份记录上述授权,所以升级后可能重新询问;改用 Developer ID 签名即可保持稳定。 ## 架构 diff --git a/artifacts/README-macOS-universal.txt b/artifacts/README-macOS-universal.txt index 5edb2ed..6c9c03b 100644 --- a/artifacts/README-macOS-universal.txt +++ b/artifacts/README-macOS-universal.txt @@ -1,4 +1,4 @@ -Shift 0.1.4 - macOS 通用(universal) +Shift 0.1.5 - macOS 通用(universal) 本文件说明 macOS 安装包是怎么打出来的、在其它机器上会遇到什么,以及如何自己校验。 完整细节见仓库 docs/RELEASE.md 的「macOS packaging」。 @@ -30,11 +30,15 @@ Intel 都能用。它既是新机器的首次安装方式,也是软件内升 macOS 权限 截图与录屏需要「屏幕录制」,输出目录需要「文件与文件夹」,带声音录屏需要 - 「麦克风」。Shift 会在打开截图遮罩前先检查屏幕录制权限,被拒绝时给的是可操作 - 的提示,而不是一张全黑截图。 - 注意:ad-hoc 构建每次的代码签名哈希都不同,而 macOS 把「屏幕录制」这类授权绑在 - 这个哈希上,所以一次升级后可能需要重新授权——这与手动重装是同一后果。要彻底消除 - 它,需要 Developer ID 证书加公证(见仓库 docs/ROADMAP.md 的 M5)。 + 「麦克风」,「发送到设备」需要「本地网络」。Shift 会在打开截图遮罩前先检查屏幕 + 录制权限,被拒绝时给的是可操作的提示,而不是一张全黑截图。 + 「本地网络」被拒绝时比较安静:Shift 照常发出广播,也能回应主动找它的实例,但收 + 不到组播,于是设备列表一直是空的。若看不到其它终端,请到「系统设置 → 隐私与安全 + 性 → 本地网络」确认 Shift 是打开的;那里可能留着多条目,因为每次重新构建都是一 + 个新身份,请对准当前安装的那一个。 + 注意:ad-hoc 构建每次的代码签名哈希都不同,而 macOS 把「屏幕录制」「本地网络」 + 这类授权绑在这个哈希上,所以一次升级后可能需要重新授权——这与手动重装是同一 + 后果。要彻底消除它,需要 Developer ID 证书加公证(见仓库 docs/ROADMAP.md 的 M5)。 软件内升级 设置 → 软件更新 里检查并安装:Shift 自己下载 .dmg,先核对字节数与 SHA256, diff --git a/docs/RELEASE.md b/docs/RELEASE.md index bfcbd98..92f816e 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -117,8 +117,10 @@ with no manifest key, and the DMG covers the first install anyway. Closing this for good means an Apple Developer ID: `Developer ID Application` + `notarytool` + `stapler staple`. Then the DMG opens on double-click with no pane to visit, -and Screen Recording approval stops resetting between builds because the identity stops -changing. +and the privacy grants keyed to that identity — Screen Recording, and Local Network, which +is what device discovery needs — stop resetting between builds. That reset is not +theoretical: a 0.1.4 user found the device list empty after upgrading, with nothing in the +UI to say why. ## Publishing @@ -327,13 +329,13 @@ test, which is the proof that the check is real and not a pass-through. Checked against the live `releases` branch of this repository: -Version **0.1.4**, checked by downloading each artifact back from the raw endpoint rather +Version **0.1.5**, checked by downloading each artifact back from the raw endpoint rather than trusting the local copy: | Key | Artifact | Verified from the remote | | --- | --- | --- | -| `macos` | `Shift-macOS-universal.dmg` (54,220,806 B) | bytes downloaded, SHA256 matches the manifest | -| `windows` | `Shift-Setup-0.1.4-win-x64.exe` (23,237,844 B) | bytes downloaded, SHA256 matches the manifest | +| `macos` | `Shift-macOS-universal.dmg` (55,504,368 B) | bytes downloaded, SHA256 matches the manifest | +| `windows` | `Shift-Setup-0.1.5-win-x64.exe` (24,521,557 B) | bytes downloaded, SHA256 matches the manifest | | `windows-arm64` | not published | by choice — see "Supported release targets" | | `linux` | not published | by choice: Linux is a build target here, not a shipped product | diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index ea73a17..db1d6d9 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -113,8 +113,10 @@ names what is still missing. once accompanied it was dropped rather than kept as a second thing to maintain. The `macos` manifest key has to stay a DMG anyway, because the in-app handoff mounts it with `hdiutil`; see "macOS packaging" in `docs/RELEASE.md`. A Developer ID plus notarization removes the - prompt entirely and would also stop Screen Recording approval from resetting between - builds. + prompt entirely and would also stop Screen Recording and Local Network approval from + resetting between builds — both are keyed to the signing identity, so an ad-hoc rebuild + loses them, and a lost Local Network grant empties the device list with no message + anywhere in the UI. - Signed Windows installer: pending. - Manifest signing is done. `scripts/release-key.py` mints the release key, `publish-release.sh --key` publishes a detached `shift-update.sig` over the manifest's diff --git a/package.json b/package.json index ca90514..ed7ee73 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "shift", "private": true, - "version": "0.1.4", + "version": "0.1.5", "type": "module", "scripts": { "prepare:ocr": "bash scripts/prepare-ocr-assets.sh", diff --git a/src-tauri/Cargo.lock b/src-tauri/Cargo.lock index cae93b6..e48cce1 100644 --- a/src-tauri/Cargo.lock +++ b/src-tauri/Cargo.lock @@ -3899,7 +3899,7 @@ dependencies = [ [[package]] name = "shift" -version = "0.1.4" +version = "0.1.5" dependencies = [ "base64 0.22.1", "calamine", diff --git a/src-tauri/Cargo.toml b/src-tauri/Cargo.toml index 689d30f..e2638d1 100644 --- a/src-tauri/Cargo.toml +++ b/src-tauri/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "shift" -version = "0.1.4" +version = "0.1.5" description = "A radial file utility with screenshot, recording and OCR." authors = ["Shift Contributors"] edition = "2021" diff --git a/src-tauri/tauri.conf.json b/src-tauri/tauri.conf.json index b8c2bce..0f4006b 100644 --- a/src-tauri/tauri.conf.json +++ b/src-tauri/tauri.conf.json @@ -1,7 +1,7 @@ { "$schema": "https://schema.tauri.app/config/2", "productName": "Shift", - "version": "0.1.4", + "version": "0.1.5", "identifier": "app.nex.shift", "build": { "beforeDevCommand": "pnpm dev",