The first step would be to get more detailed 'crash' information. We use madExcept in all our software to do this (there are others too) which provides a solid stack trace when an exception occurs. Without such info you don't know what to look for....
The language designer can save to a .lng file. See; FMX.Types.TLang - RAD Studio API Documentation (embarcadero.com)
Can also create a txt-file template then load from txt-file latter then save as a .lng file.
The format of .lng files looks binary but not too complex - a section of strings (xxxx) one per line to translate then sections for a language code and translation pairs (xxxx=yyyy) one per line.
This is a great interview with Anders Hejlsberg done recently. I learned a few things I didn't already know about the history of Delphi and why certain things in the programming world evolved the way they did. Anders has a very unique perspective from working at both Borland and Microsoft for as long as he has.
I'm guessing that Anders is a few years younger than me from what he said here, and I can certainly appreciate the value of being able to look back on 40+ years of an industry that you watched get born and grow up.
Dave Nottage replied to schaumermal's topic in General Help
The uninstall didn't remove the AppData\Roaming\Embarcadero\BDS\22.0 folder. Delete the AndroidManifest.xml file in that folder, and restart Delphi. You'll also need to delete the AndroidManifest.template.xml file from your project, and rebuild.