Missing translation: en| - Unable to set language on Firefox

[aaronraimist]

Recently I've seen lots of people reporting that they are seeing missing strings for languages that are properly translated. I've also gotten bit by this a few times. The console error that looks relavent is

Unable to set language 
Object { err: null, response: XMLHttpRequest }
rageshake.js:61:8

I got it on /develop, other people on /app have reported the same issue.

[aaronraimist]

Possibly related: #4136 / #8710

#8879
#7847

[turt2live]

Looks like we might be eagerly deleting files which causes 404s later on. Might need a different cache strategy

[lampholder]

@turt2live - eagerly deleting when? When we redeploy?

[turt2live]

yes, it seems like we're blowing away the old build when we deploy a new build, which means that people who are unlucky will have missed the bundle.

[bwindels]

We could solve this by adding a service worker that adds the language files (and others) to the cache and falls back to it on a 404

[kixiQu]

This is happening for me and other people using the Riot that I host since I upgraded. The thing is, reload doesn't help. The error message is the same. Is there a header I can set with nginx to kill the caching?

[Yoric]

I keep being bitten by it several times per week, so I'd be happy if we could fix this 👍

Relevant console message seems to have changed:

Using WebAssembly Olm
Unable to set language null KeyboardShortcuts.tsx:272:21
    n KeyboardShortcuts.tsx:272
    Z init.tsx:114
Skin loaded

Could we possibly init an auto-reload when we detect the issue?

[Gustry]

I got this issue many times per week as well, for the last 2 months, a popup telling me "missing translation". But it was only a single popup. Not more.

But since yesterday, it all strings provided by Element which are pre-fixed by "Missing translation" as you can see on the screenshot

[t3chguy]

Clear your browser cache.

[Gustry]

Thanks, it worked.

[ara4n]

I'm seeing reports of this every few days atm, including from VIPs. Can Element not load the resource via JS with a retry schedule if it fails?

[Yoric]

Clear your browser cache.

Unfortunately, most end users know nothing about the cache, so we need a better solution.

[Gustry]

Clear your browser cache.

Unfortunately, most end users know nothing about the cache, so we need a better solution.

Yes, and this issue came back a few times already since my last answer. I thought it would be ok just one time, but no.

[babolivier]

I'm getting this almost every time I load Element Web now. For what it's worth, it goes away with a simple refresh of the page, but it's still pretty annoying.

[jryans]

Just to add a counterpoint, I haven't seen this in many months, at least on develop. I wonder if it's something related to cache headers...?

[babolivier]

If that helps, I should add that I'm always using develop.element.io with Firefox on Linux.

[jryans]

Okay, good to know. Unfortunately, rageshakes don't help too much for this issue at the moment, as all they show is:

E Unable to set language null

Let's at least record the actual error to the logs...

For the moment though, the next time someone does see this on develop, please capture the actual missing file from the error, as I'd like to trace down why it's been removed.

[babolivier]

^ is all I can see in the console (logs start when the Element Web tab is loaded and end a few messages after the "Unable to set language" error)

[andybalaam]

I got this again this morning, rageshake ^

[andybalaam]

Got this again today.

[novocaine]

#21605 has been merged

[andybalaam]

Just seen it again today, with updated=1 in the URL :-(

[novocaine]

Just seen it again today, with updated=1 in the URL :-(

rageshake please

[andybalaam]

rageshake please

Sorry, forgot to mention that rageshake immediately above that comment is mine.

[lindhe]

Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...

[t3chguy]

Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...

Unfortunately feedback doesn't include logs for privacy reasons, please send logs from Settings > Help & About

[novocaine]

Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...

Element 1.10.11 was created on April 19, so doesn't have the most recent attempt to fix the issue

[babolivier]

I saw it again this morning on develop, I've rageshaken ^

[babolivier]

It's happened to me again this morning, except this time it seemed to prevent Element to load (I got an infinite spinner until I reloaded the tab), so I couldn't rageshake.

[andybalaam]

I got the infinite spinner this morning. Console:

Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src"). moz-extension:33:9
Unable to set language Error: Failed to load i18n/languages.630445c.json, got 404
    getLangsJson languageHandler.tsx:533
    on_end index.js:294
    on_state_change index.js:244
rageshake.ts:72:27
Loading Worker from “https://develop.element.io/ad35579c7db15f5fe93e.worker.js” was blocked because of a disallowed MIME type (“text/html”). develop.element.io

Address bar:

https://develop.element.io/?updated=850a250cea91-react-1c70696b1020-js-d190cdc307f1#/room/!LjeDfEINUDXfGPPsHm:matrix.org

The screen is blank except for "missing translation: en|Logout" at the bottom, and a spinner in the middle.

[babolivier]

I got it again this morning. I managed to rageshake through the console ^

[andybalaam]

I got it again today (not the freeze), rageshake ^, URL: https://develop.element.io/?updated=850a250cea91-react-1c70696b1020-js-d190cdc307f1#/room/!HtSAtjJmFcbeysRBii:envs.net

[babolivier]

Also had one just now (not the freeze), rageshaken ^

[babolivier]

Again ^

[turt2live]

It's unclear what this was blocked on, but it's certainly worthy of picking up.

I believe at this point we know what causes it, we just need to figure out how to fix it.

[richvdh]

Is this still happening? I don't remember seeing it recently.

[andybalaam]

I haven't seen it for ages. Closing. If it re-occurs please re-open. (Thanks Rich for pointing this out.)