Skip to content

[BUG] apm view --file does not find a recorded file when the path is given in NFD form (macOS Finder drag-and-drop) #3687

Closed

Description

Describe the bug

macOS file dialogs and Finder drag-and-drop produce NFD-normalized paths. apm view --file "<NFD absolute path>" exits 2 with "outside the project deploy root"; an NFD relative path exits 1 with "origin unknown ... do not assume it is safe to edit", although the file is recorded and APFS treats both spellings as the same file.

Expected behavior

NFC and NFD spellings of a recorded path resolve to the same provenance.

Found by the 0.36.0 pre-release lifecycle sweep, round 2 (#3649). The affected command is new in 0.36.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/cliCLI command surface, flags, help text (cross-cutting).pillar/consumePillar: install any agent package into any harness, reproduciblypriority/lowHuman-set low priority; does not imply acceptance, implementation approval or a release target.type/bugSomething does not work as documented.

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions