Andee lives on your phone or Mac and uses any app like you do—no integrations, no root, any model; memory and passwords never leave your device | Andee 住进你的手机或 Mac,像你一样操作任何 App——无需集成、无需 Root、支持任意模型,记忆和密码绝不离开设备。
docs(mac): the Gatekeeper instruction was for macOS 14, not 15
booboosui8743eb01b69b
diff --git a/desktop/README-signing.md b/desktop/README-signing.mdindex 556b739..1212822 100644--- a/desktop/README-signing.md+++ b/desktop/README-signing.md@@ -39,10 +39,32 @@ security list-keychains -d user -s $(security list-keychains -d user | tr -d '"'## What users see-The certificate is not from Apple, so Gatekeeper still blocks the first open of-a downloaded copy: right-click Andee → Open, or System Settings → Privacy &-Security → Open Anyway. Once. After that, and after every update signed with-the same certificate, Accessibility and Screen Recording stay granted.+The certificate is not from Apple, so Gatekeeper refuses the first launch of a+downloaded copy.-Removing that first-open step needs an Apple Developer ID ($99/year) and+**On macOS 15 (Sequoia) and later, "right-click → Open" does not work any more** —+Apple removed that override, and it is still what most of the internet says, so+expect users to have been told the wrong thing. The current path is:++1. Double-click Andee; it is refused. Dismiss the dialog.+2. System Settings → Privacy & Security → scroll to **Security**.+3. A line names Andee as blocked, with an **Open Anyway** button beside it.+4. Confirm, and authenticate.++⚠️ The button only appears for **about an hour** after the failed launch attempt.+If it is missing, launch Andee again and go straight back to Settings — this is+the single most common reason someone reports "there is no such button".++Once done, and after every update signed with the same certificate, Accessibility+and Screen Recording stay granted.++Removing that step needs an Apple Developer ID ($99/year) andnotarization; pass its identity with `-Pandee.signing.identity`.++### Do not tell users to run `xattr -d com.apple.quarantine`++It comes up in every forum thread and it does make the dialog go away — by+removing the flag that records the file came from the internet, for *any* file,+including one that should have been blocked. It teaches a habit that defeats the+check everywhere. The Settings path costs one extra step and keeps the mechanism+that asks about the next app.diff --git a/docs/releases/v0.6.0.md b/docs/releases/v0.6.0.mdindex ec8bd9b..0dd62d4 100644--- a/docs/releases/v0.6.0.md+++ b/docs/releases/v0.6.0.md@@ -11,10 +11,23 @@ now starts on CodeFlying** rather than on-device, and the Mac app exists at all.> **These binaries are unsigned or locally signed, and bare.** The APK is the `debug` build — the release> build type has no `signingConfig` and this repository has no keystore, so `assembleRelease` emits an> APK that will not install until you sign it. The two `.dmg`s are signed with a **local identity, not an-> Apple Developer ID**, so Gatekeeper blocks the first open of a downloaded copy: **right-click Andee →-> Open**, or System Settings → Privacy & Security → **Open Anyway**. Once. After that, and after every-> update signed the same way, Accessibility and Screen Recording stay granted. Removing that step needs a-> Developer ID ($99/year) and notarization, which this project does not have.+> Apple Developer ID**, so Gatekeeper will refuse the first launch of a downloaded copy.+>+> **On macOS 15 (Sequoia) and later the "right-click → Open" trick no longer works** — Apple removed it,+> so most advice you will find online is out of date. Do this instead:+>+> 1. Double-click **Andee**. It will be refused. Dismiss the dialog.+> 2. Open **System Settings → Privacy & Security** and scroll to **Security**.+> 3. There is a line naming Andee as blocked, with an **Open Anyway** button. (Its label differs by+> system language — look for the button next to the app's name, under **Security**.)+> 4. Confirm, and authenticate.+>+> ⚠️ That button **only appears for about an hour** after the failed launch. If you do not see it, launch+> Andee again and go straight back to Settings.+>+> This is needed once per copy. After that, and after every update signed with the same identity,+> Accessibility and Screen Recording stay granted. Removing the step entirely needs a Developer ID+> ($99/year) and notarization, which this project does not have.>> All binaries are built with **no keys configured** — no CodeFlying key, no voice-provider key. See> **[Download](#download)** for what that means and what to supply yourself.@@ -153,8 +166,9 @@ will name what is missing — that is the self-check working, not a fault.## Known issues-- **The Mac build is signed with a local identity, so Gatekeeper blocks the first open** and there is no- notarization. The one-step workaround is above; removing it needs an Apple Developer ID.+- **The Mac build is signed with a local identity, so Gatekeeper refuses the first launch** and there is+ no notarization. The Settings route above is the only way through it on macOS 15 — the old+ right-click override is gone — and it needs doing once per copy. Removing it needs an Apple Developer ID.- **A Mac build made on another machine, without that machine's signing keychain, is ad-hoc signed** —its identity is locked to the build's hash, so installing it over an existing copy makes macOS treat itas a **different app**: Accessibility and Screen Recording must be granted again, and a stale switch