Permission denied
You can’t approve translations without review access. Ask your workspace owner to update your role.
Documentation
Find quick fixes for the most common problems.
Support
Import failed
Usually a typo in the file, or a placeholder that doesn’t match the original text.
GitHub problems
A pull request didn’t appear, or a sync failed. Check your repository access and file paths.
AI isn’t working
AI may be switched off for the project, or a usage limit may have been reached.
The most common error: placeholders
Some text has blanks that your app fills in later, like {count}. If the original says {count} but the translation says {c}, StringsOS flags an error so your app doesn’t break. Make sure the placeholders match exactly.
- Check the placeholder names
- Check the file for typos
- Remove any trailing commas
Files
Imports usually fail for two reasons: a typo in the JSON file (like a missing comma or an unescaped quote), or a placeholder that doesn’t match the original text. Check your file with a JSON checker before uploading. If a placeholder doesn’t match, edit the translation so it matches the original.
AI
First, check that AI is switched on in your project settings. If it is but suggestions still fail, you may have hit a rate limit, or our AI provider may be having a temporary outage. Check the StringsOS status page for known issues, and make sure your text has enough context for the AI to work with.
GitHub
If pull requests aren’t being created, check that the StringsOS GitHub App has write access to your repository. Then check that the file paths in your project settings match your repository exactly. StringsOS can’t send updates if a path doesn’t exist.
Still need help?
Email us with the project name, what you were doing, and any error message you saw.
Contact support
Don’t let a small problem slow down your launch.
Free during beta · No credit card required