I may have some news for you, but I'm not it's good
news sure until you try it. Before I go into that, please be patient with me while I explain a few topics and provide some insight into dependency alignment.
I noticed that you have no active support, this is completely fine and is usually an indication that a previous license has expired. However, in your case, you have never
downloaded or received a license (trial or paid) for any Telerik product with this account. This means you should not have access to, or be developing with, Telerik UI for Xamarin.
It is common that a company will purchase the license and you are the developer. If this is the case, please contact the account holder and have them assign you as the Licensed User
. It literally takes 15 seconds to switch the license to your account (they will remain the owner and can switch users at any time).
1. Go to Manage Licensed Users Portal
2. Unassign the license from the company account (they will remain the owner of the license
3. Assign the license to you (using your email
This will allow you to download and install newer versions and open priority support tickets. Okay, let's move onto the technical topics!
Prerelease and Latest Version Support
UI for Xamarin will never officially support a prerelease or experimental version of Xamarin.Forms. The officially supported minimum version must be a stable release from Microsoft. Although newer versions usually work, we do not build with or test with those newer versions.
It's important to remember that when UI for Xamarin R1 2019
was released, Xamarin.Forms 4 was not released yet. Thus, UI for Xamarin 2019.1.x was released with XF 3.6
support. When XF 4 was pushed into the stable channel, it was a major release with significant
breaking changes from Microsoft.
We will try to match the next major Telerik release with the latest version of Xamarin.Forms (the next major release is 2019 R3
). We may or may not use XF 4.0 as the version of XF that we build on depending on what kind of problems that brings to our users who still need XF 3.6.
Utimately, we will avoid bumping the minimum version of XF in the middle of a release (i.e. 2019 R2 SP1) unless it is absolutely necessary.
Let's discuss the current UI for Xamairn release, 2019 R2. It has the minimum version of Xamarin.Forms set to 3.6. Using newer "officially unsupported" version of Xamarin.Forms usually
works, but there are always breaking changes from Microsoft when they bump the major version number (i.e. 2.x -> 3.x -> 4.x) and we cannot guarantee it will.
2019 R2 SP1
Today was a big release for 2019 R2, the first Service Pack (aka SP1). We have many fixes for XF 4 problems in this release. I recommend trying it to see it if it fixes your issue.
If it doesn't then I ask that you follow my previous instructions on providing a reproducible. This will allow me to get the developers involved and work on a fix for the next service release (we do smaller service release about once a month).
Fixing Problems in XF 4.x
In the cases that there is a problem, this is when we ask that you provide an isolated, clear reproducible. With this test project, we can isolate the issue and include a fix in a service release (even though we don't officially support that version).
This is what has been happening in the past few service releases, there were a few problems with breaking changes in XF 4 that we could resolve, while keeping XF 3.6 as the minimum version.
Thank you for your patience and understanding while reading my explanations. I hope it helps clears things up and you understand how the release cycle is aligned.
If today's release doesn't help, please consider opening a Bug Report Ticket
with the reproducible attached (important!) so that we can work on getting a fix out as soon as possible.
Lance | Technical Support Engineer, Principal
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items