Completed
Last Updated: 18 Aug 2017 13:33 by Simba
ADMIN
Nikolay
Created on: 31 May 2017 12:08
Category: Calendar & Scheduling
Type: Bug Report
2
Calendar: Appointments are shown with offset from the original date depending on the device local Timezone.
Available in minor release 2017.2.0818. It will also be available in the R3 2017 release.
7 comments
Simba
Posted on: 14 Aug 2017 21:08
Thanks for the fix telerik
Glenn Henriksen
Posted on: 08 Aug 2017 09:41
I hit the same issue and worked around it with a custom renderer: 
public class CustomCalendarRenderer : CalendarRenderer
{
    public override bool TrySetViewMode(CalendarViewMode view, bool isAnimated)
    {
      if (view == CalendarViewMode.Day)
      {
        this.Control.DayView.DayEventsViewStyle.TimeLabelFormat.TimeZone = TimeZone.GetTimeZone("UTC");
      }
      return base.TrySetViewMode(view, isAnimated);
  }
}
Simba
Posted on: 14 Jul 2017 07:05
Hi Amitesh

I suppose we are the few who have raised this issue for review but i would suggest to use a workaround for the moment rather than render it useless. Basically in my result appointment source, i check for (Device.RuntimePlatform == Device.Android) and then convert my start and end time to universaltime. This worked for me an i hope it points you in the right direction for your case until this has been addressed by telerik
Amitesh
Posted on: 13 Jul 2017 21:08
Can you please atleast confirm that it would be done in the next 2 weeks. If not we will now need to remove the calendar from our product as it renders useless.
ADMIN
Stefan Nenchev
Posted on: 26 Jun 2017 07:30
Hello,

Unfortunately, we cannot provide you with exact information when the behavior will be investigated at our end. Currently, we are working on other issues with higher priority, however, we will make sure to address this issue at some point as well. You can follow the item in order to subscribe to automatic notifications.

Simba
Posted on: 25 Jun 2017 11:10
At least tell us which release we should expect this fix
Amitesh
Posted on: 19 Jun 2017 20:49
Please get this fixed as soon as possible as it is affecting our release.