10-12-2017 10:35
10-12-2017 10:35
I have a very simple TextInput right now:
<TextInput settingsKey='code' label='Code' />
In my companion code on the settingsStorage.change event, the event key is correct ("code"), however the newValue returns a JSON string "{"name":"1234"}" instead of the expected value "1234". Is this expected behavior?
Answered! Go to the Best Answer.
10-18-2017 16:44
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
10-18-2017 16:44
It's a known issue and we'll be looking to fix this in the future.
10-18-2017 16:44
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
10-18-2017 16:44
It's a known issue and we'll be looking to fix this in the future.
09-16-2018 17:11
09-16-2018 17:11
Is this fixed?
Best Answer09-16-2018 17:12
09-16-2018 17:12
Is there a workaround?
Best Answer12-30-2018 08:35
12-30-2018 08:35
I am using this workaround
<TextInput
label="IP:PORT"
value={props.settings.address}
onChange={value => props.settingsStorage.setItem('address', value.name)}
/>
Best Answer04-13-2019 13:10
04-13-2019 13:10
Still not working correctly?
08-17-2021 17:40
08-17-2021 17:40
Has it been fixed with SDK 6? SDK 4.3 still has this issue especially using a for loop for multiple contacts
[ '{"name":"+"}', '+1212', '+1212', '+1212' ] Where the first retrieved has this issue and then the rest don't. It creates a consistency issue.
08-17-2021 17:59
08-17-2021 17:59
Using .name on those values returns null, because it should be ."name" which returns a error
Best Answer