Update Device service changing time zone

[Tiago Ramos]

In my app, the register device service is automatically and correctly setting the device's time zone (in the case of my test device, GMT-3.

However, when I call the update device service to set a custom value, even though my service call makes no mention of timezone, it's still setting the device's timezone to uct.

If there's no option other than sending the proper value for the timezone every time I call the update device service (which I'd rather not do), how can I get information about the device's timezone?

[Nikita]

Hello,

Please look at this link:

https://developer.mozilla.org/en-US/d...

[EJLD]

Hi There, I time to time get UTC instead of GMT+XX:00 .
I need that GMT+... how to param that field pls ?
thks

[Evgene Karachevtsev]

Hello Eric,

Is your format UTC or GMT - it depends on your response, but you always can format your UTC to GMT with help of JS. For example, http://stackoverflow.com/questions/51...

[EJLD]

Hi Evgene, thks for your msg and the link.
however, not sure it will solve my problem which is quite simple.
pls see att'd screenshots.
1/ until yesterday I got in the devices table the GMT+09:00 well displayed. that is perfect to me.
2/ since yesterday that I reinstalled the app on both devices I use for tests, I got "UTC" only instead.
GMT or UTC are ok with me as long as I can get the timezone "+XX:00" included in the string.

Did I set something wrong ? are you aware of a change somewhere ?

thks in advance,
Eric

[Evgene Karachevtsev]

Hello Eric,

Unfortunately it looks like the bug. Could you please share your project with support, tell us its name and steps to reproduce?

[EJLD]

Hi Evgene, thks for your prompt reply.
the app name is o2o4pw
and the DB name is mybnoteDB
you'll find att'd 2 screenshots.
1/ login
2/ service querying for the timeZone

thks for your time
Eric

[Yurii Orishchuk]

Hi EJLD,

I tried this and can confirm that's a bug.

We have posted this bug to our developers team.

And will let you know here as soon as this bug will be fixed.

Only way to workaround it is to pass previous value in "timeZone" field.

Details: http://prntscr.com/6c1uvm/direct

Regards.

[EJLD]

thks for acknowledging.
and for the work around. I'll check it out later.
Eric