Troubleshoot

Translation shows as squareCopy Anchor Link

See this section to learn how to fix this.

---

Localized content not appearingCopy Anchor Link

• Verify the Localization Settings asset is located in a Resources folder (for example, Resources/Localization Settings.asset; see the supported paths).
• Check that [Evo Localization] GameObject appears in the Hierarchy at runtime (under DontDestroyOnLoad).
• Ensure your table keys match exactly (keys are case-sensitive).
• Enable Enable Logs in Localization Settings to see detailed error messages in the Console.

---

Language not changingCopy Anchor Link

• Make sure all languages have content for the keys you're using.
• Check the Console for localization warnings (enable Enable Logs in Settings).
• Verify the Update Mode on Localized Objects is not set to OnDemand.

---

Dynamic strings not workingCopy Anchor Link

• Verify the keyword in your localized text uses the format {keyword} with curly braces.
• Ensure the variable name in Dynamic String configuration matches exactly.
• Check that the reference object is assigned and not null.
• Set the target variable to the exact name of an instance field or readable, non-indexed property, rather than a literal replacement value.
• Call UpdateContent() after changing the value if the text needs to update immediately.

---

RTL SupportCopy Anchor Link

Evo Localization supplies translated strings and delegates text rendering to the selected component. TMPText uses TextMeshPro; the UniText integration assigns strings to UniText. Configure text direction, shaping, and fonts in the renderer you use.

---

Google Sheets sync problemsCopy Anchor Link

See Google Sheets troubleshooting for sharing, header, GID, and token checks.

---

UniText option missingCopy Anchor Link

Install the media.lightside.unitext package and resolve compilation errors. The option is compiled conditionally through the package's assembly version defines. See UniText setup.

---