{"version":"2.1.272","anchor":"bug-fix-bridgeqr-output-split-used-stale-variable","canonical_anchor":"bug-fix-bridgeqr-output-split-used-stale-variable","heading":"Bug fix: bridge\/QR output split used stale variable","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.272\/e\/bug-fix-bridgeqr-output-split-used-stale-variable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.272","markdown":"### Bug fix: bridge\/QR output split used stale variable\n\nFixed a bug where bridge QR-code text output could be built from stale, unresolved data\n\n**What**\n\nThe routine that renders a bridge connection's QR code as text (using a UTF-8, low-error-correction QR encoder) was splitting the wrong variable into lines: it used the value captured before an asynchronous operation completed, instead of that operation's actual resolved result. This is now fixed.\n\n**Why**\n\nThe previous behavior could have produced stale or empty QR-code text output instead of the correct, up-to-date code.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}