Troubleshooting
My translations are not reaching my app
Almost always because the language is translated but not published: editing and publishing are deliberately two different things.
Run through these quick checks. For every cause and its fix, see Why are my translations not reaching my app?
- Is the language published? Editing a translation does not publish it. Open Releases and check that the language has a live version. See Publish a locale.
- Was it published after your change? A published version never changes. Publish the language again to include edits made since.
- Are AI drafts held back? If the project holds drafts back, a Glossa draft reaches your app only once someone approves or edits it.
- Is your app pinned to a version? A versioned address serves that version forever. Point your app at the latest address, or at the new version.
- Is a cache still serving the old version? Give a new publish about a minute.
- Does your app read files from its build? If your build pulls translations with the CLI or the GitHub Action, nothing changes until you run that build again. Publishing affects only the CDN.
- Is it the right kind of key? Your app reads the CDN with a CDN key. A deploy token is for the CLI and the API, not the CDN. See Connect your app to the CDN.