One way to work around this is to set a new items source.
Setting the cell style properties for border width to 0 does not remove the borders.
The reason for the exception is that when the IsBusy of the indicator changes, the Content is added to and removed from the visual tree. Because it is data-bound, the chart immediately tries to notify its native counterpart that an update is necessary, and the iOS control is looked up. However, sometimes, the old iOS control is found, which has been disposed. A possible workaround is not to put content inside the busy indicator. Use the busy indicator as a simple overlay. Available in the R3 2018 SP release.
If you set both properties, the background color stands on top of the image. Available in minor release 2018.1.202. It will also be available in the R1 2018 SP release.
Workaround: Use the Small Percentage(http://www.fileformat.info/info/unicode/char/FE6A/index.htm) or Fullwidth Percent Sign(http://www.fileformat.info/info/unicode/char/ff05/index.htm).
If you have set MaxDate in the Calendar and you swipe the view to see the previous month, it is not possible to navigate back to the month that has the MaxDate. If you change the month through the MonthView -> everything starts working. Available in the 2018 R2 SP release.
When the SelectionMode of the RadCalendar is Range and you have set a MaxDate - you should not be able to select dates after the MaxDate. However, swipe-selecting cells which are disabled is working. Available in the R3 2018 SP release.
If the AutoComplete is visualized in a second (nested) view controller, the control stops autocompleting. Available in the R1 2018 release.
If the control is hidden when initializing and then on a later stage is visualized, it hangs.
An exception is thrown when the AutoComplete is hosted inside a horizontal StackLayout.
When the AUtoComplete is bound to an ObservableCollection and you add/remove items from the collection -> the changes are not applied in the AutoComplete in iOS and Android. The UWP implementation works as expected. Available in minor release 2017.3.1214. It will also be available in the R1 2018 release.
Available in the 2018 R2 SP release.
When there are only two items in the ItemsSource and users reorder them, the underlying collection is not reordered Edit: Avalable in R3 2017 SP release.
Available in the R3 2018 SP release.
When you install the Progress Telerik UI For Xamarin application on an iOS Device, navigate to some example and try to view its code - the application hangs. The issue is fixed in the latest version of the application.
When creating a Xamarin.Forms solution using the Telerik project wizard, the individual projects are not named properly. See the attached screenshots for reference: Screenshot1 - File > New, where I named the solution "MySolutionName" Screenshot2 - After project generation, the individual projects are still using "Telerik.Xamarin.XXX" when it should be "MysolutionName.Mobile.XXX"
Available in minor release 2017.2.0721. It will also be available in the R3 2017 release.
https://drive.google.com/file/d/0BzMkrUMZyQ6FWC1scXZVTmhVOEk/view?usp=sharing