Closed Bug 1994209 Opened 10 months ago Closed 10 months ago

Translation feature stopped working in 145.0 beta 1

Categories

(Firefox :: Translations, defect, P1)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1994147
Tracking Status
firefox145 blocking fixed

People

(Reporter: pascalc|PTO, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

Attached image Screenshot of the error

We have reports that Firefox Translation is broken in 145.0b1
https://old.reddit.com/r/firefox/comments/1o6gwci/translating_completely_broken_with_ff_145_beta/

I and a colleague can confirm.

It works in 146 Nightly ( Mozilla/5.0 (X11; Linux x86_64; rv:146.0) Gecko/20100101 Firefox/146.0 ID:20251013142147)

Translations: The engine failed to load for translating "de -> en". Removing it from the cache. Error: No bergamot-translators were found that matched the major version: 4
    <anonymous> resource://gre/actors/TranslationsParent.sys.mjs:2629
    #getBergamotWasmBlob resource://gre/actors/TranslationsParent.sys.mjs:2650
    getTranslationsEnginePayload resource://gre/actors/TranslationsParent.sys.mjs:1644
    receiveMessage resource://gre/actors/TranslationsEngineParent.sys.mjs:52
TranslationsEngineChild.sys.mjs:148:18
Flags: needinfo?(enordin)
Status: NEW → RESOLVED
Closed: 10 months ago
Duplicate of bug: 1994147
Flags: needinfo?(enordin)
Resolution: --- → DUPLICATE
No longer regressed by: 1982594

Update 1

The move from Firefox 144 to Firefox 145 transitions the Translations service to communicate with the RemoteSettings collection translations-wasm-v2 instead of translations-wasm (v1).

The issue is that the WASM binary in the translations-wasm-v2 collection unintentionally had a filter expression on it that restricted the record to only Nightly and local builds.

When the beta build rolled over to 145.0b1, Firefox could no longer retrieve the WASM binary due to the filter.

I have already removed the filter, and everything should be fixed once 145.0b1 Firefox builds automatically re-sync their Remote Settings data.

This issue is isolated only to the 145.0b1 build, only on this day, and requires no code changes to fix.


UPDATE 2

I've confirmed the fix by installing the RemoteSettings Devtools Extension (GitHub) on 145.0b1 and resyncing Remote Settings manually.

Translations will work again once RemoteSettings re-syncs.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: