Skip to content

fix: finalmask domains drop proxies from the app subscription - #47

Open
AnonymousContributorAlpha wants to merge 2 commits into
hiddify:devfrom
AnonymousContributorAlpha:fix/finalmask-platform-attr
Open

AnonymousContributorAlpha wants to merge 2 commits into
hiddify:devfrom
AnonymousContributorAlpha:fix/finalmask-platform-attr

Conversation

@AnonymousContributorAlpha

Copy link
Copy Markdown
Contributor

One-line fix for a regression from 526eadf (feat: add finalmask support to hiddify-core).

Bug: hiddify-core/client/snippets/finalmask gated on ctx.platform.hiddify_core.version, which doesn't exist on the client PlatformVar (client side exposes ctx.platform.hiddify / .singbox / .xray). Any proxy bound to a domain carrying a finalmask extra therefore failed its render with 'PlatformVar' object has no attribute 'hiddify_core', and the panel dropped that whole outbound from the hiddify-core/singbox profiles: all xhttp/ws/grpc/httpupgrade vless/vmess/trojan configs bound to such domains vanished from the Hiddify app subscription, while sub-link/clash/xray profiles kept them.

Fix: gate on ctx.platform.hiddify.version, matching the other hiddify-core client fragments; the >= 5.0.0 intent is preserved.

Verified on a live 14.0.0b13 panel (domains with finalmask extras, HiddifyNext/5.0.0 UA): render errors 24 -> 0, with HiddifyNext/2.7.0 the configs render without the finalmask field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant