You’re welcome. Do you also see the new entry in your LanguageModelGeneratorLookupList.text that is in your app bundle? If it is in there, it is in the correct alphabetical position, and matches the other entries as far as there being a tab between the uppercase word and the uppercase pronunciation (where each part of the pronunciation is separated by exactly one space) it ought to be picked up with no issue. If you’re using the sample app build and the acoustic model is being rebuilt each time, make sure you’re making your original change to the copy of the text file that is in the acoustic model project. If you aren’t, you should be able to directly edit the file that is in the acoustic model bundle that has been added to your app.
Keep in mind that there can’t be a space between “HEY” and “NEXAR”, they have to be one word in the lookup list, i.e.:
HEYNE HH EY N HEYNEXAR HH EY N EH K S AA R HEYS HH EY Z