When you have declared a custom GroupHeaderTemplate and the total height of the elements within it is bigger than the pre-allocated one - the content is visualized on top of the group's items.
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
The SelectionChanged event of the ChartSelectionBehavior is fired twice for a single selection change
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.
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:
Our version info:
- Build server is using Microsoft's hosted agent with Visual Studio for Mac 18.104.22.168 (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 ?
Available in minor release 2018.3.1122. It will also be available in the R1 2019 release.
Available in minor release 2018.3.1109. It will also be available in the R1 2019 release.
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.
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.
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.