[Bug] Cannot import subscriptions or local YAML profiles

[enshindev]

Description

I am unable to import either a remote subscription or a local YAML profile in Omash.

Both import methods fail, but there is no error message or useful log output.

Steps to reproduce

Remote subscription

1. Open Omash.
2. Try to import a valid Mihomo/Clash subscription URL.
3. Enter the subscription URL and press Enter.

Local YAML

1. Open Omash.
2. Try to import a valid Mihomo/Clash YAML file.
3. Select the local YAML file and press Enter.

Actual behavior

After pressing Enter, the import dialog becomes unresponsive.

• The dialog appears to freeze.
• Pressing Escape does not close the dialog.
• After a few seconds, the dialog closes automatically.
• The profile is not imported.
• No error message is displayed.

Expected behavior

• Pressing Enter should start the import process.
• A valid remote subscription should be downloaded and imported as a profile.
• A valid local YAML file should be imported as a profile.
• If the import fails, an appropriate error message should be displayed.
• The dialog should remain responsive while the import is in progress.

Logs

I checked the Omash Supervisor logs with:

journalctl --user -u omash-supervisor.service -f

However, there are no errors related to the import operation. The logs only show service lifecycle messages such as:

Started Omash Mihomo Supervisor.
Stopping Omash Mihomo Supervisor...
Stopped Omash Mihomo Supervisor.

Environment

• OS: Arch Linux
• Distribution/environment: Omarchy
• Compositor: Hyprland
• Architecture: x86_64
• Mihomo: Mihomo Meta 1.19.29
• Omash: 0.1.2/0.1.3

Additional information

The subscription URL and local YAML configuration are valid and can be used successfully with other Mihomo/Clash clients.

If there is a dedicated log file or a way to enable debug logging for Omash, please let me know where I can find it.

I can provide additional logs, a sanitized YAML configuration, or other debugging information if needed.

Thanks!

[ourongxing]

I haven’t run into this issue before. First double‑check that your subscription link is valid. You can fix this directly using Codex or other code agents, then open a PR.