blakeslee-research/nucleic-remote-ios
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remote Store Scope

Browse Source 
Nucleic-Session: F8081386-339F-46B4-A6A9-A0F53F618D34
Co-authored-by: Nucleic <[email protected]>
This commit is contained in:
abkslm
2026-07-06 17:17:16 -07:00
co-authored by Nucleic
parent 14aa335f6e
commit 7aa27af3af
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
NucleicRemote/Shared/ApproveFromActivityIntent.swift
+9 -3
View File
@@ -7,12 +7,18 @@ import NucleicProtocol
/// "resolve from the lock screen without unlocking" path (docs/APP_INTENTS_OPPORTUNITIES §4.1).
///
/// It lives in the **Shared** group so both the app and the widget extension can reference it in
/// `Button(intent:)`. The widget extension links no `NucleicProtocol`, so this intent carries plain
/// `String` ids and compiles its real work only into the app (`#if canImport(NucleicProtocol)`).
/// That's sound because iOS runs a widget/Live-Activity button's intent in the **app's background
/// `Button(intent:)`. It carries plain `String` ids and compiles its real work only into the app,
/// gated on `#if NUCLEIC_APP` (a custom compilation condition set on the app target only). That's
/// sound because iOS runs a widget/Live-Activity button's intent in the **app's background
/// process** — where `RemoteStore` owns the live E2EE channel — never in the extension. The
/// extension-side copy exists solely to satisfy the `Button(intent:)` type reference.
///
/// NB: the guard is `#if NUCLEIC_APP`, *not* `#if canImport(NucleicProtocol)`. `canImport` tests
/// module findability, not linkage — and because the app builds `NucleicProtocol` into the shared
/// DerivedData products dir, it's findable from the widget extension too. So `canImport` is `true`
/// in the extension, which would compile this branch there and fail on the app-only `RemoteStore`
/// / `IntentError` types. `NUCLEIC_APP` tracks target membership, which is what we actually mean.
///
/// Not discoverable in Shortcuts/Spotlight: it's button-only, driven by ids embedded at render time
/// (a human uses `AnswerApprovalIntent` for the spoken/Shortcuts path).
struct ApproveFromActivityIntent: AppIntent {