fix(client): accept native capability combinations in loopback gate

Keep the v5 loopback gate strict on protocol and identity while accepting valid native capability combinations. This fixes false Client-not-found results for capable Windows packages without changing runtime behavior.
This commit is contained in:
AAA authored and GitHub committed 2026-09-04 04:00:51 +08:00
1 parent 5781d6bbfa
commit dbfa26a778
1 file changed
+4 -4
+4 -4
View File
@@ -97,10 +97,10 @@ async function browserHandshake(
const health = await response.json();
if (health.protocol === ${NATIVE_PROTOCOL} && health.service === "screener-client" &&
health.port === port && typeof health.instanceToken === "string" &&
health.nativeMedia?.video === false &&
health.nativeMedia?.processAudio === false &&
health.nativeMedia?.systemAudio === false &&
health.nativeMedia?.hardwareH264 === false) {
typeof health.nativeMedia?.video === "boolean" &&
typeof health.nativeMedia?.processAudio === "boolean" &&
typeof health.nativeMedia?.systemAudio === "boolean" &&
typeof health.nativeMedia?.hardwareH264 === "boolean") {
return { port, instanceToken: health.instanceToken };
}
} catch {} finally {