You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c9f2fef
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: AGENTS.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -253,12 +253,12 @@ The following records earlier approaches. For current behavior, authorization, a
253
253
254
254
Read [DEVELOPER.md](DEVELOPER.md) before changing signing, App Groups, installation, file creation, or monitored folders. It is the current source for those contracts and their verified evidence.
255
255
256
-
- Host and extension share `MoreMenu/Shared` sources: document catalog, preferences, file creation, target resolution, and home-directory policy.
256
+
- Host and extension share `MoreMenu/Shared` sources: document catalog, preferences, file creation, target resolution, and monitored-volume policy.
257
257
- Both products use the App Group `QN24ZH7M6W.GMX.MoreMenu`, authorized by the matching certificate-backed signing Team ID. Local builds reject ad-hoc signing.
258
258
- Preserve consent during upgrades. Migrate the two legacy preferences through the signed host import command; retain old data and never read the unauthorized legacy group from the extension.
259
259
- Use exclusive file creation and retry only filename collisions. Preserve existing contents and propagate other failures.
260
-
- Monitor filtered visible top-level home folders once at initialization. Exclude home/filesystem roots, Library, Applications, and packages. External volumes remain out of scope.
261
-
-Desktop-specific behavior is deferred at the user's request. Keep the existing fallback unchanged until that investigation resumes.
260
+
- Monitor `/` plus every visible mounted volume, and update the set on mount, unmount, and rename. Release a volume on `willUnmount`. See DEVELOPER.md for the 2026-10-03 evidence (Desktop background and home-rooted windows need `/`).
261
+
-Build the menu without file-metadata reads; resolve the destination only in the menu action.
262
262
- Validate with `./scripts/test.sh`, then inspect a signed Release build. Reboot/Finder UI behavior requires live manual validation; passing unit tests alone is insufficient.
263
263
- The app opens Finder's extension-management interface through `FIFinderSyncController.showExtensionManagementInterface()`. Settings paths vary by macOS version.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-3Lines changed: 20 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,37 @@
2
2
3
3
## Unreleased
4
4
5
+
### Added
6
+
7
+
-**The menu now works everywhere in Finder:** on the Desktop background, in windows rooted at the home folder, in any folder on the startup disk, and on external and network drives. The extension monitors `/` plus every mounted volume and updates the set when a drive is mounted, renamed, or unmounted. A drive is released before it unmounts, so MoreMenu cannot block ejecting it.
8
+
- Each Finder menu request is logged with its menu kind and target, so a missing menu can be told apart from a skipped callback.
9
+
5
10
### Fixed
6
11
7
-
- Authorize shared preferences with the signing Team-ID-prefixed App Group. The installed app's repeated AppData prompt was traced to an unauthorized `group.GMX.MoreMenu` container, despite Apple Development signing. This supersedes the earlier signing-only diagnosis below.
12
+
-**Repeated privacy prompts.** Three causes were found and removed:
13
+
- Shared preferences now use the Team-ID-prefixed App Group `QN24ZH7M6W.GMX.MoreMenu`, which the signing certificate authorizes. The old `group.GMX.MoreMenu` container was unauthorized, so macOS asked "access data from other apps" again for every extension process.
14
+
- Stored privacy answers were bound to the hashes of old ad-hoc builds. Answers given to a certificate-signed build stay valid across rebuilds signed with the same certificate.
15
+
-`test.sh` unregisters its unsigned test build from Launch Services and PlugInKit. Stray copies with the same bundle IDs could be loaded by Finder under a different code identity.
16
+
- A right-click alone can no longer start a folder-privacy check. The menu is built without reading file metadata; the destination folder is resolved only after a command is chosen.
17
+
- No menu in the Documents column of a home-rooted window, and none on the Desktop background. Finder did not consult the extension there while it monitored only top-level home folders.
8
18
- Create new files exclusively and retry filename collisions without replacing existing data.
9
19
- Reject unresolved target metadata rather than creating in a guessed parent folder; show creation errors.
10
20
- Preserve consent and preferences during local upgrades, verify staged signatures, and restore the previous app if migration or registration fails.
11
21
12
22
### Changed
13
23
14
-
- Share one file-type catalog and preference contract between app and extension.
24
+
- The extension sandbox allows writes on every volume (`temporary-exception.files.absolute-path.read-write = /`, previously home only). Read-only locations report an error after the click instead of hiding the menu.
25
+
- Full Disk Access for MoreMenu.app is the recommended setup. With it enabled, the extension created files on the Desktop and in Downloads without any prompt (verified on macOS 26.6.2). Without it, macOS asks once per location type.
26
+
- This reverses the 1.2.2 narrowing below. That change was based on a misdiagnosis of the AppData prompt, whose real cause was the unauthorized App Group.
27
+
- Share one file-type catalog, preference contract, and monitored-volume policy between app and extension.
15
28
- Add behavioral Swift tests, installer/signature tests, a shared Xcode test scheme, and CI checks.
16
29
- Require certificate-backed signing for local packages; public releases require Developer ID signing and notarization credentials.
17
30
- Use the Finder Sync extension-management API for settings navigation and label file-type checkboxes for accessibility.
18
-
- Desktop-specific behavior remains deferred.
31
+
32
+
### Not yet verified
33
+
34
+
- After a restart, that the "access data from other apps" prompt stays away while `/` is monitored.
35
+
- On an external drive: adding the drive when it is connected, creating a file on it, and ejecting it.
Copy file name to clipboardExpand all lines: DEVELOPER.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
./scripts/install-local.sh
9
9
```
10
10
11
-
`test.sh` runs script tests and standalone macOS unit tests. The tests compile the same Shared sources as the app and extension, without launching the host app or running the installer. The shared Xcode scheme also builds the app and extension to catch integration errors. Xcode 16.2 or later is required; the deployment target remains macOS 14.
11
+
`test.sh` runs script tests and standalone macOS unit tests. The tests compile the same Shared sources as the app and extension, without launching the host app or running the installer. The shared Xcode scheme also builds the app and extension to catch integration errors. Xcode registers that unsigned build with Launch Services, so `test.sh` unregisters its build products on exit; otherwise Finder could load the test copy and TCC would see a different code identity. Xcode 16.2 or later is required; the deployment target remains macOS 14.
12
12
13
13
`build-app.sh` builds a universal Release app, signs the extension before its containing app, and verifies both signatures and entitlement sets. By default it selects an available Apple Development identity. Override with `MOREMENU_CODE_SIGN_IDENTITY`. It rejects ad-hoc signatures and signing teams that do not match the App Group. No app is installed by this command.
14
14
@@ -21,7 +21,7 @@ Build/test output is under `.build/` by default. `MOREMENU_TEST_DERIVED_DATA` ov
21
21
-`MoreMenu/Shared/DocumentKind.swift`: the 19 persistent file-type identifiers, UI/menu titles, extensions, categories, and initial contents.
22
22
-`Shared/MenuPreferences.swift`: the shared defaults contract and idempotent legacy import.
23
23
-`Shared/DocumentFileCreator.swift`: exclusive filename creation with numbered retries.
24
-
-`Shared/HomeDirectoryScope.swift`: home-boundary and monitored-directory policy.
24
+
-`Shared/FinderMonitoringScope.swift`: the monitored set — the boot volume root plus every mounted volume.
25
25
-`Shared/TargetDirectoryResolver.swift`: file-versus-folder resolution; failed metadata reads propagate as errors.
26
26
-`MoreMenu/SettingsStore.swift`: observable settings shared by all settings windows.
27
27
-`MoreMenuExtension/FinderSync.swift`: Finder callbacks, target acquisition, menu presentation, file opening, and error feedback.
@@ -44,15 +44,19 @@ Sources: [App Group authorization](https://developer.apple.com/documentation/xco
44
44
45
45
### Sandbox write capability
46
46
47
-
The extension retains`com.apple.security.temporary-exception.files.home-relative-path.read-write = ["/"]`. In this entitlement, `/` means the user's home. The host has no broad file-write entitlement. External volumes remain out of scope. This task does not expand write capability or add Apple Events permissions.
47
+
The extension uses`com.apple.security.temporary-exception.files.absolute-path.read-write = ["/"]`, so the sandbox allows writes on every volume. POSIX permissions and TCC still apply. The host has no file-write entitlement. App extensions must be sandboxed, so this temporary exception is the sandbox capability for local and Developer ID builds; it is not suitable for the Mac App Store.
48
48
49
49
### Folder privacy and Finder monitoring
50
50
51
51
Sandbox capability does not override macOS privacy decisions. Normal folder-access permissions and App Group authorization must be diagnosed separately.
52
52
53
-
Finder monitoring remains limited to visible top-level home subfolders, excluding `Library`, `Applications`, and packages. Set `directoryURLs` exactly once at extension initialization, using `HomeDirectoryScope.monitoredDirectoryURLs()`. Keep this conservative policy; the old notes attributing every AppData prompt to monitoring scope are not sufficient evidence to change it.
53
+
Finder consults a Finder Sync extension only for clicks inside its monitored folders. On 2026-10-03 (macOS 26.6.2), with only top-level home folders monitored, Finder did not call `menu(for:)` for the Desktop background or for a column-view window rooted at the home folder. BetterZip, whose extension monitors all mounted volumes, appeared in both menus.
54
54
55
-
`FinderSyncInvariantTests` exercises the actual folder-selection policy against temporary filesystem fixtures and retains one structural guard for the single registration assignment.
55
+
The extension therefore monitors `/` plus every visible mounted volume (`FinderMonitoringScope.directoryURLs`). `/` does not cover other mounts, so each volume is listed explicitly. The set is recomputed on mount, unmount, and rename. A volume is released on `willUnmount`, so Finder Sync cannot block ejecting it.
56
+
57
+
The May 2026 note that blamed `/` monitoring for the AppData prompt predates the App Group fix. Confirm with a reboot test that the prompt stays away.
58
+
59
+
`FinderSyncInvariantTests` covers the monitored-set policy and guards two structural rules: one `directoryURLs` assignment, and no file-metadata reads while building the menu.
56
60
57
61
## Preference migration
58
62
@@ -78,11 +82,11 @@ Files use `untitled.ext`, `untitled_0001.ext`, and subsequent numbers. Rich text
Desktop background and cloud-managed Desktop behavior are explicitly outside this patch. The existing AppleScript insertion-location fallback is retained; its missing Apple Events sandbox authorization is a known limitation, not a supported Desktop guarantee. Do not broaden monitored roots or add automation entitlements as part of these reliability fixes.
87
+
`menu(for:)` logs the menu kind and the targeted URL. No log line for a right-click means Finder did not consult the extension. A line with `target=nil` means MoreMenu returned an empty menu. For a desktop icon, Finder reported `~/Desktop`as the target.
84
88
85
-
For the later investigation, log whether Finder calls `menu(for:)`, the menu kind, and whether a target URL exists. Distinguish callback suppression from MoreMenu returning an empty menu before proposing a fix.
89
+
The AppleScript insertion-location fallback cannot work: the extension lacks Apple Events entitlements, and tccd logs that refusal.
86
90
87
91
## Settings navigation
88
92
@@ -119,7 +123,7 @@ The workflow uses a temporary keychain and removes its signing material afterwar
119
123
1. Run `./scripts/test.sh`; include concurrent creation, preservation, RTF, settings migration, scope policy, signing rejection, and installer rollback checks.
120
124
2. Build and verify a signed app. Inspect both products' Team ID, App Group, sandbox entitlement, and hardened runtime.
121
125
3. After an actual local upgrade, confirm prior selections survive and only the intended installed extension is used.
122
-
4. Test file creation and errors inside supported Finder folders, and verify out-of-home locations have no commands.
126
+
4. Test file creation on the Desktop background, in home-rooted windows, and on an external volume. Check the error for a read-only location, and confirm that ejecting a drive still works.
123
127
5. Relaunch the host/extension and reboot. Confirm the logs authorize the group and the repeated AppData prompt does not return. A successful build or one launch does not establish reboot behavior.
124
128
6. Check the settings-management button and error dialog on macOS 14, 15, and 26 before claiming compatibility beyond compilation.
0 commit comments