Element-web: Missing translation: en| - Unable to set language

[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: https://github.com/vector-im/riot-web/issues/4136 / https://github.com/vector-im/riot-web/pull/8710

https://github.com/vector-im/riot-web/issues/8879
https://github.com/vector-im/riot-web/issues/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?