Calling getLocalizedText on Missing String Crashes Windows Simulator

Hello, devforum! I was working on my project today and ran into this crash. I’m not sure if it’s windows-simulator-specific, and would appreciate it if some others would try it out, perhaps.

What happened:
Calling on a string that doesn’t exist in the localization file causes the simulator to exit instantaneously with no error or feedback.

with en.strings empty or not containing the proper definition for “anything”

Expected behavior:
I personally would find it much nicer if it fell back to the unlocalized string in the case there is no localization. At the very least, it would be nice if there were an error message.

1 Like

This will be fixed in the next release, thanks for the report.