I am working with events and timeline for my first time for a client prototype. In the app, the time event shown in timeline is not matching the event real time (in my time zone). Couriosly in the web dashboard the time in the time line is correct. Is this a wrong behavior in the app or something that can be configured (like tz or so)?
Added links to images of the app timeline and web timeline to make it clear.
Yes, it’s the Android app (version 13). I use of Blynk.logEvent to trigger the event and I make sure that it’s triggered just once when the event occurs (avoid loop conditions). The events are reported correctly in the app when they are triggered but the time is not the right one. In the web dashboard the timeline reports both event and time correctly. About the server, the app is hosted through https://blynk.cloud/ (I am sorry, I don’t know if that is the server you are referring to).
I did verified the phone TZ and is set right to GTM-6 (image below). In next pictures it’s seen the phone time and the latest recent event. There is still an offset in the time.
But next is interesting… I did a test and changed the time zone to GMT-8 (Pacific Time) and looks that effectevely in this case the timeline time follows correctly the phone time.
But this is much more interesting… it did changed the phone back to my time zone but instead of using the name of the country to set the TZ I did use the utc offset time like in next picture:
and it worked and resolved the timeline time issue:
For some unknown reason (in this phone) the automatic TZ definition in the phone using the country location sets correctly the time in the phone but screws up the time in the timeline (maybe a daylight time issue?).
Setting the TZ using the UTC offset sets the time in the phone correctly and in the timeline (crazy thing considering that the phone interface reports UTC-6 in both configuration methods).
Thanks guys for all the follow up in this case and hope it helps other colleagues in same situation.
In the first case - maybe it was some app cached timezone. We will check if that’s some app-side issue.
From the UI I assume it is a Samsung device, am I right?