// Guides

Fix Missing Localizations

Strings not translating? Checklist for diagnosing missing iOS or Android localizations — covers language setup, sync state, and empty base values.

Use this checklist when strings appear untranslated.

Common Symptoms

You may need this guide when:

A new app string exists in base language but not in one or more target languages.
A translation row exists but value is empty.
Rows remain in New or NeedsReview longer than expected.

Checklist

Confirm base language is attached and active.
Confirm target language is attached and active.
Verify the source string is marked as translatable.
Check whether base value is blank (blank base values are not queued for translation).
Re-run sync and inspect NeedsReview vs New states.

Empty Value Requeueing

Existing localized rows with empty values can be requeued when the base variant still has meaningful content.

Fast Recovery Workflow

Fix language attachment or source content issues first.
Re-run sync/import.
Check whether missing rows were created for each active non-base language.
Confirm queued rows move from pending to translated or review-ready states.

If base value is empty, fill the base string first and sync again. Empty base strings are intentionally not queued for translation.

Repository vs Manual Upload Behavior

Manual upload projects may prune rows missing from source payload.
Repository projects generally preserve existing localized rows unless keys are removed.

Common Mistakes

Expecting non-base rows when base language is not set correctly.
Uploading stale manual files and assuming current source coverage.
Treating non-translatable keys as missing translation defects.
Debugging target language first when base value is blank.