Follow-up: every route that sends a file now carries this morning's fix
A short follow-up to the hotfix earlier today. Two older reply routes, both switched off at the moment, still held the broken version of the file-sending step. Nothing about how the product behaves changes today — this closes the last ways the same fault could have come back, and records the audit that confirmed nothing else was left exposed.
Highlights
- The two switched-off reply routes now carry the same fix as everything else
- Every place the product attaches a file was audited — twelve in all, none left exposed
- Campaign, single-send and group attachments confirmed working after this morning's fix
- No action needed and no re-scan required; this changes nothing you can see today
In this release2
- ImprovedMedia
The two switched-off reply routes carry the fix as well
Auto-replies have two generations of engine behind them. The older one has been switched off since WhatsApp introduced its privacy identifiers, because it cannot read those conversations at all; everything you send and receive today runs on the newer one, which is what this morning's hotfix repaired.
The older engine was left holding the broken version of the file-sending step. It is unreachable, so nothing was failing through it, but switching it back on later would have quietly reintroduced the same fault — pictures vanishing while text carried on working, with nothing in the release notes to connect the two.
What we changed:
- Both routes in the older engine — the step-by-step reply sequence and the single reply with a file attached — now go through the repaired file-sending step, exactly as the live engine does.
- The fix is applied once per reply rather than once per file, so a sequence sending several pictures pays for it a single time.
Nothing you can see changes today. This is here so the fix stays fixed when that engine is brought back.