Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

The sample app does not respond to locale change settings #597

Closed
6 tasks
aashwinGaur opened this issue Apr 2, 2018 · 5 comments
Closed
6 tasks

The sample app does not respond to locale change settings #597

aashwinGaur opened this issue Apr 2, 2018 · 5 comments

Comments

@aashwinGaur
Copy link

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.

Briefly summarize your issue

I want the sample app to start with "en-US" locale . I changed the value to "en-US" in AlexaClientSDKConfig.json file also confirmed that the settings.db file has the value en-US. I re-compiled after changing the settings. But the app always starts with en-IN . I can change the locale by typing in the settings options in the terminal . But i have disabled the input as i wanted alexa to start on boot .

What is the expected behavior?

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?

  <x.y.z>

Tell us what hardware you're using:

  • Desktop / Laptop
  • [ --->] Raspberry Pi
  • Other - tell us more:

Tell us about your OS (Type & version):

  • Linux
  • MacOS
  • [ --->] Raspbian Stretch
  • Raspbian Jessy
  • Other - tell us more:
@kclchan
Copy link
Contributor

kclchan commented Apr 2, 2018

Hi @aashwinGaur, by changing the "locale" in terminal, does the setting persist after quitting and starting the SampleApp (without recompiling)? If that's possible, are you using the same json file with the same database file after disabling input?

@aashwinGaur
Copy link
Author

Yes it persists.
And i am using the same json file . The weird part is that after compiling if i look at the json file in the "build" folder it shows locale setting as en-US but en-IN is active .

@kclchan
Copy link
Contributor

kclchan commented Apr 4, 2018

Hi @aashwinGaur, thanks for the feedback. We are looking into this issue and will let you know of any findings ASAP. Thanks!

@dhpp
Copy link
Contributor

dhpp commented Apr 18, 2018

@aashwinGaur, we have identified the root issue, and this will be fixed in an upcoming release of the SDK. Thanks for bringing this to our attention.

@aashwinGaur
Copy link
Author

Thank you

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants