{"version":"2.1.239","anchor":"device-bash-withheld-telemetry-field-is-always-false","canonical_anchor":"device-bash-withheld-telemetry-field-is-always-false","heading":"\"device bash withheld\" telemetry field is always false","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/device-bash-withheld-telemetry-field-is-always-false","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### \"device bash withheld\" telemetry field is always false\n\nA new telemetry field about withheld device shell access always reports false on this build.\n\n**What**\n\nTwo telemetry events now report a `device_bash_withheld` field, but the helper that supplies its value for the bind event is compiled down to a constant false. The feature it describes is never active on this build and the field always reports false.\n\n**Details**\n\n- Events affected: `tengu_device_bridge_started` and `tengu_device_bind_prepared`.\n\n**Evidence**\n\n`device_bash_withheld`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}