Summary
Creating or opening a note tile causes the app to try to read a file path of undefined, which fails with an ENOENT from the desktop file bridge.
Observed error:
Error: Error invoking remote method 'fs:readfile': Error: ENOENT: no such file or directory, open 'C:\Users\arkouda\AppData\Local\Programs\Collaborator\undefined'
Reproduction
- Create a
note tile via the collab canvas tools/UI.
- Open or render the tile.
- The app attempts to read a file path and throws the ENOENT above.
What I observed
- A
code tile includes a real filePath in its tile metadata.
- A
note tile does not include filePath.
- The failing path resolves exactly like a missing
filePath is being passed into the desktop fs:readfile bridge and normalized into the Collaborator app directory.
Expected behavior
note tiles should be treated as in-memory content, or otherwise avoid file reads unless a valid backing path exists.
Likely fix
Guard file-backed tile loading by tile type and reject missing filePath before calling fs:readfile. In particular, note should not flow through the same file-loading path as code/other file-backed tiles.
Summary
Creating or opening a
notetile causes the app to try to read a file path ofundefined, which fails with an ENOENT from the desktop file bridge.Observed error:
Reproduction
notetile via the collab canvas tools/UI.What I observed
codetile includes a realfilePathin its tile metadata.notetile does not includefilePath.filePathis being passed into the desktopfs:readfilebridge and normalized into the Collaborator app directory.Expected behavior
notetiles should be treated as in-memory content, or otherwise avoid file reads unless a valid backing path exists.Likely fix
Guard file-backed tile loading by tile type and reject missing
filePathbefore callingfs:readfile. In particular,noteshould not flow through the same file-loading path ascode/other file-backed tiles.