UI is displayed in a Slavic language

[heviiguy]

Describe the bug

Rather than the Garmin Express settings for the app being displayed in English as all of my other settings are, the UI is displayed in a Slavic language

I have:

• [x] Used HTTPS to access HomeAssistant (with a public certificate)
• [x] Checked that my JSON Syntax is correct (options 2, 3, or 4 or otherwise)
• [x] Checked that my JSON follows the schema (options 2, 3, or 4)
• [x] Used the online editor to check my JSON against HomeAssistant (option 1)
• [x] Checked the Docs
• [x] Checked the Troubleshooting Guide

To Reproduce Steps to reproduce the behavior:

1. Go to '.Garmin Express.'
2. Click on '.GarminHomeAssistant(application)..'
3. Scroll down to '."three dots"...'
4. See error

Expected behavior English UI

Screenshots GarminHomeAssistant:

Typical:

Garmin Device (please complete the following information):

• Model: [Fenix 6 Pro]

Additional context In "Garmin Express" when attempting to set-up the application

[philipabbey]

Because the other apps don't offer Slavic translations?

[heviiguy]

Because the other apps don't offer Slavic translations?

No idea. I only know that I've not selected the UI to be in this language. EVERYTHING else is in English, as expected. Currently, I have absolutely no idea what the selection boxes refer to!

How can it be ensured that the initial Garmin Express setting dialogue for your app communicates in English? If this is a bug without a solution, could you please indicate what each selection box is asking for? At least then I can complete the set-up.

[heviiguy]

Seems that this is not an isolated issue (yeah, I'm also running a Sonoma 14 Macbook)...

https://forums.garmin.com/developer/connect-iq/i/bug-reports/garmin-express---wrong-language

https://forums.garmin.com/developer/connect-iq/f/discussion/388137/incorrect-language-displayed-for-custom-data-fields

It probably has something to do with Garmin's SDK rather than with your app . As it doesn't appear that Garmin is doing anything to resolve this, would you please:

"indicate what each selection box is asking for?" Thanks in advance.

[philipabbey]

And this bug is not consistent either. I can't recreate it with Garmin Express Ver 7.20.3.0.

Thank you so much for your investigation to track down those two links above. In the case of this app, we do not create resources-eng as a copy of the default. This point relates to both links that suggests we ought to, but then another user says that workaround did not work. We're then left with the inconsistency issue which means I cannot test for a fix even if I do repeat the resources-eng\strings\strings.xml file.

Now I've avoided updating Garmin Express since I use the mobile app instead, and its a pain to keep the Windoze desktop PC updated all the time (the application must be installed on a proper Admin account not just with elevated priviledges or things go wrong as I recall).

Do you need me to provide a trial installer with the default strings copied to resources-eng for you to sideload and try?

[heviiguy]

Thanks for your comments, @philipabbey. And thanks for your offer of the trial installer. Alas, I've not a clue of how I'd go about sideloading it 🤪. What would be much easier, I think, is to just show me (and anybody else suffering from this issue) a couple of screen shots showing the settings comments in English. That way I (we) can enter the relevant data and get this puppy running!

[philipabbey]

Thanks for your comments, @philipabbey. And thanks for your offer of the trial installer. Alas, I've not a clue of how I'd go about sideloading it 🤪. What would be much easier, I think, is to just show me (and anybody else suffering from this issue) a couple of screen shots showing the settings comments in English. That way I (we) can enter the relevant data and get this puppy running!

Please see the documentation here:

https://github.com/house-of-abbey/GarminHomeAssistant#settings

[heviiguy]

Got it. Thank-you very much, Phillip!

[philipabbey]

I'm going to close this issue on the grounds that there's a bug in Garmin Express that I cannot resolve. Thanks for taking the time to report and then research the issue, very helpful! I might add a note to the Known Issues section of the documentation so that we have a record.