Blocker crash with fonts (it seems)

Hey,

I recently bought I2 Localization and yes, it's a great asset and a huge time saver. However..

I'm facing an issue right now and I haven't found any solution so far.
I created a font term and I added 3 translations for it :
French and English use the same font (same asset, same name). However, arabic needs to have a different font.
I'm applying these fonts as a secondary term on a Text component in Unity UI. I set pre-localize on Awake at true.

I play my game and everything works fine. Then, I stop the player, add a new term directly in the I2Languages prefab. A simple text. This step seems important in order to reproduce the bug, apparently it triggers it. I don't use this new term anywhere and I simply play the game again.

When I try to show a text that has the font as a secondary term, there is a crash :

ArgumentException: An element with the same key already exists in the dictionary.

This comes from the following function in LanguageSource :

public void UpdateAssetDictionary()
{
Assets.RemoveAll(x => x == null);
mAssetDictionary = Assets.ToDictionary(o=>o.name);
}


This bug happens systematically. I can't access the corrupted term in the prefab, the UI is broken. Therefore, I cannot delete it or change it. The only way I can get out of this is reimporting my spreadsheet that doesn't have the font term and quit unity (if I try to create the term again without quitting Unity, I get the crash immediately).

Also, this started happening after I changed my PC's language from French to English for some testing (but I don't know if there is any connexion)

Is there a way I can fix this ? or perhaps I've been doing something wrong without knowing and you could give me the best practice ? This is quite blocker.

Attachements : the logs in Editor Console Pro + the broken UI on the corrupted term

Many thanks,

Thank you for your reply. Will add that fix and will download your update when it goes live.

In the meantime, the bug stopped occuring. In my multiple and weird maneuvers, I probably did something that ended up cleaning the asset database from its duplicates.

Cheers,