Selecting a file to archive tasks into forces selecting a directory instead of a file

[TangentFoxy]

Bug Report

App Version: 2.0.27

Platform: macOS

Installation Method: Direct Download

Location of todo.txt files: Local on the machine

Expected Behavior:
The file selection dialog should let me select files.

Actual Behavior:
It only let me select directories and excluded all files.

Steps to Reproduce:

1. Click archive button on a file with no set archive file.
2. Click "Open file".
3. Attempt to navigate to a file.

Screenshots:

---

Is it just looking at the name, seeing it ends with .txt, and assuming this is a file?

I was going to redo this to make a more clear example of the problem, but now I cannot unset this directory as the archive file, and I'm afraid that if I accidentally click archive, I will lose data and/or cause a crash as it attempts to write data directly to a directory.

[TangentFoxy]

I'm looking at the code in Dialog.ts and while I have no experience with Electron, this looks correct according to dialog's documentation.

[TangentFoxy]

Oh it seems this is related to electron/electron#11391 and I'm duplicating a known issue #413 here. It also looks like an Apple problem to me. That's really unfortunate. Edit: It seems like they're using the Apple API incorrectly.

For anyone stumbling across my thing, I managed to work around it by changing the filter to all files in the dialog, so that I could open the directory and then select the appropriate text file.

[ransome1]

@TangentFoxy I'm on a Mac myself, but I really cannot reproduce this. May I ask you what version of macOS you're running?

[ransome1]

@TangentFoxy curious if this is this happening with the latest Electron stable in this pre-release of sleek: https://github.com/ransome1/sleek/releases/tag/v2.0.28-rc.1

[TangentFoxy]

• Tahoe 26.5.2, but I have no idea if I updated between then and now.
• v2.0.28-rc.1 does not fix the error.

Edit: I don't know if you saw, but the error is dismissed on Electron's issues tracker as a claimed macOS bug. I am not very familiar with how this stuff works, but looking at their code vs the documentation for Apple's API, they seem to be using the API incorrectly. I've been too ..not okay.. to try to see if I am correct on that. >.>