essential-ui-kit-for-xamarin.forms
essential-ui-kit-for-xamarin.forms copied to clipboard
Upgrading Syncfusion packages and xamarin breaks the layouts
Hi all, just wanted to inquire if this is the normal behaviour or it's a bug. I upgraded a project where I was using templates from the Visual Studio extension and it literally broke almost all the layouts. I upgraded Xamarin.Forms to 4.8.0.1269 and Syncfusion packages to 18.2.0.59. I am debugging using Xiaomi Redmi Note 7. Before the upgrade, everything was looking great.
Hi Takudzwa,
Greeting from Syncfusion.
We have analyzed your query and we have checked with Xamarin.Forms version 4.8 and our Syncfusion latest version 18.3.0.35 and it has been worked fine at our end. Could you please share the breaking layouts screenshots for understanding the actual problem and proceed it at our end and could you please ensure is it working fine with lower version of Syncfusion with XF version of 4.8 ?
Regards, Yuvaraj
Hi @YuvarajPalanisamy , thanks for your response. Below are the screens that are broken. I upgraded to Syncfusion 18.3.0.40 && Xamarin to 4.8.0.1560.
These screenshots were taken on a phone (Xiaomi Redmi Note 7) and it's displaying layouts as if they are on a tablet or desktop.
LR Padding

LR Padding

Some screens are crashing [This is a bug report screen showing the crash report]

On a phone, only one button is supposed to be displayed and the position of the buttons is not correct for a phone.


This table is not even showing


Did not check all screens but these are the few I managed to identify.
Hi @Tashaa78
We have checked the reported issues in our recent 4.0.0 release and we do not reproduce this issue. Can you please check with our recent release? We have attached the screenshot for your reference
https://www.syncfusion.com/downloads/support/directtrac/general/ze/UIKit-UWP-2102572411
We have tested in the below configuration.
Visual studio 2019 V 16.9.4 Android 10 and 11 Xamarin forms 5.0.0.2012
If you still have issues with the recent release, please let us know your configuration as above. So we could test in the same configuration to reproduce the issue.
Thanks Meikandan