Completed
Last Updated: 04 Sep 2019 06:30 by ADMIN
System.NullReferenceException is thrown when navigating back pages with RadListView and using Xamarin.Forms 4.0 or higher. 

UPDATE:
The issue is confirmed to be in Xamarin.Forms framework. A fix is already provided. The Xamarin.Forms 4.3 version will contain the fix.
Completed
Last Updated: 26 Jun 2019 18:42 by ADMIN
Release 2019.2.603.360 (R2 2019 minor release)
Created by: Francis
Comments: 9
Category: UI for Xamarin
Type: Bug Report
15

the following exceptions occur when upgrading to Xamarin.Forms v 4.0:

System.NotSupportedException: Unable to activate instance of type Telerik.XamarinForms.DataControlsRenderer.Android.ListView.TemplateCellContainer

System.NullReferenceException: Object reference not set to an instance of an object
  at Telerik.XamarinForms.InputRenderer.iOS.SegmentedControlRenderer.OnElementDetached


Completed
Last Updated: 12 Mar 2019 21:49 by ADMIN
Created by: Jacob
Comments: 2
Category: UI for Xamarin
Type: Bug Report
0

We can build on our personal development environments without issue. The issue is only on the Azure DevOps build server. We believe this to be related to a version incompatibility. Possibly the build server is attempting to reference an old library. We are seeing the issue on both iOS and Android builds. 

This issue is well documented here: 
https://www.telerik.com/forums/can%27t-resolve-the-reference-%27system-object#wNK1sRy19UOhttFJzbEshQ

Our version info:
- Build server is using  Microsoft's hosted agent with Visual Studio for Mac 7.7.4.1 (attached file with all software installed on the host build-host-software.txt)
- App is on version 3.4.0+
- Referenced libraries use .NET Standard 1.6 and 2.0
- Xamarin.Forms app is hosted in a .NET Standard 2.0 library

Could we get a hold of an older compatible version of the software that can work with our version if there is no workable solution here ?

 
Completed
Last Updated: 19 Jun 2019 12:55 by ADMIN
Release R2 2019 SP1
Created by: Robert
Comments: 1
Category: UI for Xamarin
Type: Bug Report
0

When trying to build the QSF example on GitHub, an error occurs due to The IHiearchyAdapter still being used in :

TreeView - First Look Example and Customizations Example.

The Error Message is Error CS0122: 'IHierarchyAdapter' is inaccessible due to its protection level (CS0122) (QSF)

Completed
Last Updated: 20 Feb 2019 12:53 by ADMIN
Remove Xamarin.Android.Support.v8.Renderscript dependency from NuGet packages dependencies.
Completed
Last Updated: 20 Feb 2019 12:48 by ADMIN
When the Lite Nuget package is referenced and the linker behavior is "SDK Assemblies Only", an error related to PdfViewer is raised.
Completed
Last Updated: 31 Jan 2019 15:47 by ADMIN
The issue can be observed in the AutoCompleteView control.
Completed
Last Updated: 31 Jan 2019 15:47 by ADMIN
ArgumentOutOfRangeException is thrown when two buttons are pressed at a time
Completed
Last Updated: 06 Sep 2019 12:26 by ADMIN
Release R2 2019 SP2

The SelectionChanged event of the ChartSelectionBehavior is fired twice for a single selection change

Completed
Last Updated: 22 Nov 2018 16:14 by ADMIN
Available in minor release 2018.3.1122. It will also be available in the R1 2019 release.
Completed
Last Updated: 25 Mar 2019 16:04 by ADMIN
ADMIN
Created by: Lance | Technical Support Engineer, Principal
Comments: 10
Category: UI for Xamarin
Type: Feature Request
2
As of 2018.2.620, UI for Xamarin will invoke approximate 600 warnings when compiling an Android project that uses SDK later than 23.

This is due to the fact that the UI for Xamarin.Android controls are built on API 23, which will surface warnings at compile time if the project consuming them is using a later version.

Although UI for Xamarin is compatible with newer version, and causes no impact on the outcome, these warnings obscure any meaningful warnings the user might have. 

This is a problem when projects are built in a CI/Cd pipeline and warnings are treated as important/significant for enterprise CD deployment (i.e. scrolling through 600 warnings to find any legitimate warnings is not practical).

Available in R3 2018 release.
Completed
Last Updated: 09 Nov 2018 13:41 by ADMIN
ADMIN
Created by: Didi
Comments: 0
Category: UI for Xamarin
Type: Bug Report
0
Available in minor release 2018.3.1109. It will also be available in the R1 2019 release.
Completed
Last Updated: 20 Jun 2018 14:31 by ADMIN
ADMIN
Created by: Stefan Nenchev
Comments: 0
Category: UI for Xamarin
Type: Bug Report
0
Available in the 2018 R2 SP release.
Completed
Last Updated: 16 Apr 2019 15:57 by Navid
ADMIN
Created by: Stefan Nenchev
Comments: 20
Category: UI for Xamarin
Type: Bug Report
30

			
Completed
Last Updated: 03 Aug 2018 06:46 by ADMIN
ADMIN
Created by: Lance | Technical Support Engineer, Principal
Comments: 1
Category: UI for Xamarin
Type: Feature Request
0
Currently, the project template generates a PCL that uses an App.cs.

Most developers who use XAML prefer to have an App.xaml in order to use global resources (or the Telerik Theming mechanism).

Please consider adding a checkbox to the Project Wizard that lets you choose between using [App.xaml/App.xaml.cs] or [App.cs]
Completed
Last Updated: 18 Oct 2018 11:49 by ADMIN
ADMIN
Created by: Stefan Nenchev
Comments: 0
Category: UI for Xamarin
Type: Bug Report
2
There are 2 approaches to customize the theme -> directly override the resources in the BlueResources dictionary or create a custom resource dictionary and merge it instead of the BlueResources one.

If you take the first approach in a .NET standard project and override one of the colors -> an ArgumentException is thrown:

Use the second approach as a workaround where you create a custom resource dictionary, copy all the colors from the original one and modify them within your custom one.

Available in the R3 2018 SP release.
Completed
Last Updated: 18 Oct 2018 11:48 by ADMIN
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.
Completed
Last Updated: 26 Feb 2018 09:49 by ADMIN
ADMIN
Created by: Pavel R. Pavlov
Comments: 0
Category: UI for Xamarin
Type: Bug Report
0
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.
Completed
Last Updated: 20 Jun 2018 14:14 by ADMIN
ADMIN
Created by: Stefan Nenchev
Comments: 0
Category: UI for Xamarin
Type: Bug Report
0
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.
Completed
Last Updated: 18 Oct 2018 11:47 by ADMIN
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.
1 2 3 4 5