Skip to content

SFM: Export log file picker appears only after changing log level #4266

Description

@max-bold

Operating system

macOS

System version

macOS Tahoe 26.5.1 Apple M4

Installation type

sing-box for macOS Graphical Client

If you are using a graphical client, please provide the version of the client.

1.13.14

Version

Description

In SFM 1.13.14, exporting logs to a file does not immediately open the path/file picker dialog.

The dialog appears only after changing the log level. After the log level is changed, the export flow continues and the path selection dialog finally appears.

This looks like a GUI state/update issue in the log export action: the export command seems to be triggered, but the file picker is not presented until another UI action, specifically changing the log level, forces the view/state to update.

Expected behavior:

When the user chooses to export logs to a file, the path/file picker dialog should appear immediately, without requiring any change to the log level.

Actual behavior:

The path/file picker dialog does not appear after starting log export. It appears only after changing the log level

Reproduction

  1. Open SFM 1.13.14.
  2. Go to the log view / service log view.
  3. Try to export the log to a file.
  4. Observe that the path/file picker dialog does not appear.
  5. Change the log level.
  6. Observe that the path/file picker dialog appears only after the log level is changed.

This is reproducible locally and does not depend on any remote server or proxy configuration.

Logs

No relevant logs are available. This is a GUI issue with the log export dialog

Supporter

Integrity requirements

  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
  • I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
  • I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions