Subscriptions don’t include ShadowTLS configs.

[ivansavra1]

Describe the bug
After some time having issues with using ShadowTLS on a client, I contacted the developer to ask them to implement ShadowTLS, and I got a reply confirming that it was already supported, so I now realize that all this time, it was Hiddify Manager not including the ShadowTLS configuration on the subscription, this has never happened with other proxies before (Including ShadowSocks)

To Reproduce
Steps to reproduce the behavior:

1. Enable ShadowSocks
2. Enable and set up ShadowTLS
3. Check the subscription and you’ll see it isn’t included

Expected behavior
ShadowTLS should be included like any other proxy configuration.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[ivansavra1]

On a separate note, I also want to add that it would be better if proxy configuration was more consistent: Right now, we can make separate domain configs for all protocols, with the exception of SS FakeTLS and ShadowTLS, I don’t think there’s a good reason to keep this limitation.

[litoosh13]

shadowTLS is only support by Hiddify next and other app won't show it

[ivansavra1]

shadowTLS is only support by Hiddify next and other app won't show it

There are apps that support ShadowTLS, like Surge and Shadowrocket (Streisand will have support for), so I consider it a bug that the subscription doesn’t include a config that I set, especially because there’s no warning of this.

[ivansavra1]

@litoosh13 Here’s a screenshot from Shadowrocket working perfectly fine using ShadowTLS from Hiddify Manager, I had to configure the profile manually since the subscription link excludes it: