VLESS config crashes sing-box 1.13.0 clients (Hiddify) — "unknown value" panic

[zackroad]

Dear Creator,

Environment

• Client: Hiddify 4.1.1 (Windows), sing-box core v1.13.0
• The same subscription works fine on iOS Hiddify (different bundled core), so the issue is specific to sing-box 1.13.0.

Problem

After importing the subscription, the client throws a FATAL panic during config
validation. One VLESS node in the list carries a field value that sing-box 1.13.0
rejects. Because validation runs over the whole config, this single bad node makes
the entire profile fail to load, so the connection keeps dropping.

Stack trace (key frames)

FATAL unknown value
panic(...)
github.com/sagernet/sing/common/format.ToString(...)
github.com/sagernet/sing/common/exceptions.New(...)
github.com/sagernet/sing-box/protocol/vless.NewOutbound(...) outbound.go:86
github.com/sagernet/sing-box/adapter/outbound.(*Manager).Create(...)
github.com/sagernet/sing-box/experimental/libbox.CheckConfigOptions(...)
github.com/hiddify/hiddify-core/v2/config.validateResult(...) parser.go:152

Likely cause

A VLESS entry contains an invalid/unsupported value — most likely an invalid flow
(anything other than empty or xtls-rprx-vision, or flow set on a node without the
required TLS/Reality transport) or an unsupported packet_encoding. sing-box >=1.13.0
validates these strictly and panics on the unknown value.

Request

Could you validate the VLESS configs and remove/fix the entries with these invalid
fields so they don't crash sing-box >=1.13.0 clients? I can share a redacted log if useful.

Thank you,
Best regards.

[mohad200521-web]

Mohamad