appointments show wrong time in different time zones due to daylight time changes.

The issue can be reproduced in scenarios:

- For US time zone 14th of march: If I click an empty slot, I have a popup that tells the time that is clicked. I click on the 9 AM slot and it says I'm clicking on "10:00". This only happens on 3/14/2021

- For European countries time zone: on 28th or march 2021 when is the daylight saving time

In a scenario where you are trying to set the AppointmentsSource of the RadCalendar in the OnAppearing event of the Page, a NullReferenceException is thrown in the Telerik.XamarinForms.InputRenderer.WinRT.CalendarAdapter UpdateAppointmentsSource method.

A workaround is to make the OnAppearing method async and await the action that sets the AppointmentSource.

The more appointments you add to the AppointmentsSource, the poorer the performance of the Calendar is. 

This can be observed when switching months in month view. In case you have a huge amount of appointments, switching the months takes time. The issue is specifically obvious when a single month contains lots of appointments(600 for example). However, it is present when you are switching months that do not have any appointments at all as well.

When in MonthView, you're navigating to WeekView on CellTap event, and DisplayDate and SelectedDate are bound to the same value, DisplayDate is not updated on iOS (works properly on Android)

The visual representation of an appointment is wrong when DayViewSettings.StartTime is set so that the appointment is initially visible

On Android,  when the user selects a date on CalendarViewMode.Month mode, the DisplayDateChanged event is fired twice and the displayed date in CalendarViewMode.Day is incorrect. 

Sometimes the display date is 4-6 months ahead/behind or just with one month.

All-day area is misaligned when the device/emulator is rotated to a different orientation.

white/dark space is shown on the top of the agenda view. This space hovers some of the vents and dates from the agenda. 
You need to scroll through the agenda and the white/dark space disappears. 

when the RadCalendar is hosted inside a ScrollView, users cannot navigate to other month using the swipe gesture

If you set SelectedDate when the Calendar control is created, does not take any effect in the UI on iOS. 

As a workaround, set SelectedDate at a later stage.

I've attached a handler to the ViewChanged event of the Calendar component.

The event fires on Android but not on UWP. I've tried changing the view type using the calendar controls and also programatically but the event is not being fired.

when showing 3 months (last month, present month and the next month) on calendar component, the next month tab is displayed twice. see the attached video

Currently the first label marking the DayStartTime is not visualized in the timeline of the DayView (and MultiDayView) on Android. This leads to inconsistency with iOS, where the first label is displayed.

When the Start and EndDate properties are changed one after another and each of them calls PropertyChanged the appointment does not render accurately. If for example there is an appointment from 3 PM to 4 PM (duration 1 hour) and the Appointment is changed to one hour earlier (from 2 PM to 3 PM) on the screen the Appointment is displayed from 2 PM to 4 PM (duration 2 hours).

Additional add appointment button is displayed when the device orientation is a landscape and the calendar view mode is Year. When switching from Year to day/multiday the issue happens in these views too.

The issue can be reproduced in the Telerik Xamarin Sample App/Calendar/Scheduling example 

Go to Year view, rotate the device in landscape mode, second + button is displayed inside the calendar title (year name)

Then rotate the device in portrait mode and go to day/multiday view,  
Rotate in landscape mode -> issue occurs. 

 

In the RadCalendar, if we set the DisplayDate to future date (For example, current date is 04-03-2024 and the display date as 08-April-2024), application gets crashed in iOS platform. This issue occurs only in iOS 17 and above versions.

Exception

NSInternalInconsistencyException Reason: UIGraphicsBeginImageContext() failed to allocate CGBitampContext: size={0, 0}