Empty Table Reference when calling LocalizedString.GetLocalizedString()

Unity Engine
,
1

Unity 2022.3.7f1
Localization Package v1.4.4

I’m at my wits end here.
I’m trying to use a LocalizedString member on a ScriptableOjbect class, but I get the following error when trying to get the localized value (Full stack below)

ArgumentException: Empty Table Reference. Must contain a Guid or Table Collection Name

So I’ve gone through all my tables, and checked that its all set up correctly. My TextMeshproUgui components all work fine with these tables. I’ve also verified that the TableReference property is not null, as seen in the first image attachment to this post.

Here is the SO in question:
9402893--1316264--upload_2023-10-11_13-21-12.png

The Artifacts Table
9402893--1316267--upload_2023-10-11_13-21-47.png

Localization Settings:

9402893--1316270--upload_2023-10-11_13-22-15.png
9402893--1316270--upload_2023-10-11_13-22-15.png541×732 104 KB

FULL STACK TRACE:

ArgumentException: Empty Table Reference. Must contain a Guid or Table Collection Name
UnityEngine.Localization.Tables.TableReference.Validate () (at ./Library/PackageCache/com.unity.localization@1.4.4/Runtime/Tables/TableReference.cs:170)
UnityEngine.Localization.Settings.LocalizedDatabase`2[TTable,TEntry].GetTableAsync (UnityEngine.Localization.Tables.TableReference tableReference, UnityEngine.Localization.Locale locale) (at ./Library/PackageCache/com.unity.localization@1.4.4/Runtime/Settings/Database/LocalizedDatabase.cs:355)
UnityEngine.Localization.Settings.LocalizedDatabase`2[TTable,TEntry].GetTableEntryAsync (UnityEngine.Localization.Tables.TableReference tableReference, UnityEngine.Localization.Tables.TableEntryReference tableEntryReference, UnityEngine.Localization.Locale locale, UnityEngine.Localization.Settings.FallbackBehavior fallbackBehavior) (at ./Library/PackageCache/com.unity.localization@1.4.4/Runtime/Settings/Database/LocalizedDatabase.cs:653)
UnityEngine.Localization.Settings.LocalizedStringDatabase.GetLocalizedStringAsyncInternal (UnityEngine.Localization.Tables.TableReference tableReference, UnityEngine.Localization.Tables.TableEntryReference tableEntryReference, System.Collections.Generic.IList`1[T] arguments, UnityEngine.Localization.Locale locale, UnityEngine.Localization.Settings.FallbackBehavior fallbackBehavior, UnityEngine.Localization.SmartFormat.PersistentVariables.IVariableGroup localVariables, System.Boolean autoRelease) (at ./Library/PackageCache/com.unity.localization@1.4.4/Runtime/Settings/Database/LocalizedStringDatabase.cs:263)
UnityEngine.Localization.Settings.LocalizedStringDatabase.GetLocalizedString (UnityEngine.Localization.Tables.TableReference tableReference, UnityEngine.Localization.Tables.TableEntryReference tableEntryReference, System.Collections.Generic.IList`1[T] arguments, UnityEngine.Localization.Locale locale, UnityEngine.Localization.Settings.FallbackBehavior fallbackBehavior) (at ./Library/PackageCache/com.unity.localization@1.4.4/Runtime/Settings/Database/LocalizedStringDatabase.cs:292)
UnityEngine.Localization.Settings.LocalizedStringDatabase.GetLocalizedString (UnityEngine.Localization.Tables.TableReference tableReference, UnityEngine.Localization.Tables.TableEntryReference tableEntryReference, UnityEngine.Localization.Locale locale, UnityEngine.Localization.Settings.FallbackBehavior fallbackBehavior, System.Object[] arguments) (at ./Library/PackageCache/com.unity.localization@1.4.4/Runtime/Settings/Database/LocalizedStringDatabase.cs:233)
Assets.Scripts.Milestones.MilestoneData.GetFormattedDescriptionText () (at Assets/Scripts/Milestones/MilestoneData.cs:84)

9402893--1316249--upload_2023-10-11_13-7-58.png
9402893--1316249--upload_2023-10-11_13-7-58.png980×113 66.1 KB

2

Thats strange. It looks like you do have a table name so im unsure why it would do that, perhaps you have another LocalizedString somewhere in the project that is not set? Can you add a check in GetFormattedDescriptionText to call IsEmpty on the LocalizedString?

3

Oh my god, you were right. There was a 2nd SO of the same type, I hadnt seen. That was the one throwing the error, which then caused any further localization to fail. I just gotta set up the keys for everything before testing it.

Thank you