Skip to main content
StringsOSFree beta
Documentation: TroubleshootingExpand nav
Back to all docs
Documentation

Quickly diagnose and resolve common errors so your team can get back to localizing.

Navigation

Find detailed solutions for common errors, configuration mistakes, and connectivity issues. This section provides debugging steps for GitHub integrations, API limits, and agent errors.

1Documentation
2Troubleshooting

Support

Permission Denied

Learn how to resolve 403 Forbidden errors when trying to approve keys without Reviewer access.

Import Failures

Troubleshoot invalid JSON syntax, unmapped locales, and placeholder mismatch errors during manual file imports.

GitHub Sync Issues

Diagnose missing PRs, failed webhook deliveries, and branch mapping errors in the GitHub integration.

AI Unavailable

Understand why AI suggestions might be disabled (e.g., project consent revoked, or organization limits reached).

Understanding Placeholder Errors

The most common error during import is a placeholder mismatch. If your source key contains {count}, but the translated JSON contains {c}, StringsOS will flag this as an error to prevent your application from crashing in production. Always ensure your interpolation variables match exactly.

  • Check variable names
  • Verify JSON syntax
  • Ensure trailing commas are removed

Data issues

When JSON imports fail, the most common causes are invalid JSON syntax (like missing commas or unescaped quotes) and placeholder mismatches. Double-check your file using a JSON linter before uploading. If StringsOS detects a mismatch between source and target variables, you'll need to correct the target translation to match the source structure.

AI issues

If you cannot generate AI suggestions, first verify that AI Consent is enabled in your Project Settings. If consent is granted but suggestions fail, it may be due to rate limits or temporary service outages with our underlying AI providers. Check the StringsOS status page for ongoing incidents, and ensure your keys provide enough context for the AI to function properly.

Integration issues

If Pull Requests are not being generated successfully, verify that the StringsOS GitHub App has been granted write access to your specific repository. Additionally, ensure that your Locale Path mappings in the Project Settings match the exact directory structure of your repository. StringsOS will fail to push updates if the specified paths do not exist.

Still need help?

If you cannot find the answer here, contact the StringsOS team with the affected project, workflow, and error details.

Contact Support

Don't let a technical issue slow down your global launch.

Get started free
Book a demo

Free during beta · No credit card required