Forum Xamarin.Forms

Child rendering behaviour mismatched after upgrading Xamarin.Forms (>4.0) in FlexLayout

HemalathaMarikumarHemalathaMarikumar USMember ✭✭
edited July 2019 in Xamarin.Forms

Hi All,

I have a simple sample with the layout structure of FlexLayout which has more number of Grid. Each Grid has two children that are

  1. Grid with Label as a child
  2. Custom View (TouchView) which is inherited from View.

    <FlexLayout HorizontalOptions="Start" 
                                    BindableLayout.ItemsSource="{Binding ChildItems}"
                            <Grid BackgroundColor="Aqua">
                                <Label TextColor="Black" Text="{Binding}"/>

Here TouchView represents like

public class TouchView:View


This FlexLayout wrap its child element correctly up to the Xamarin.Forms version of

But after , it rendered be like in below

Note : Issue only with Android platform.

@Xamariners please check this and update us with possible solution. Actually it blocks our development cycle. Taking this a high priority and provide a solution ASAP.

I have attached the sample in both lower and higher version of Xamarin.Forms.

Hemalatha M.

Best Answer


  • HemalathaMarikumarHemalathaMarikumar USMember ✭✭

    @LeonLu Thanks for your update. I will check and let you know

  • LeonLuLeonLu Member, Xamarin Team Xamurai

    Ok, waitting for you update, if the reply is helpful, please mark it as answer, it will help other who have similar issue.

  • LeonLuLeonLu Member, Xamarin Team Xamurai

    @HemalathaMarikumar Are there any updates for this issue? If the reply is helpful, please try to mark it as an answer, it will help others who have similar issue.

  • HemalathaMarikumarHemalathaMarikumar USMember ✭✭

    @LeonLu Yes. I have checked the provided solution. But in my cases, I have to arrange all children of the main grid in the same column. It really appreciated based on your solution only we have got an idea to find, that issue is because of having the problem with measured width value to the custom view (TouchView). Hence we have fixed the same in our custom control.

    Without considered our cases, it will be worked fine. Even though it should consider this as a bug.

Sign In or Register to comment.