_This issue has been moved from a ticket on Developer Community._
I have updated to the latest version of xamarin form (4.7.0.968) and all the labels are overlapping on iOS.
Image:143201-simulator-screen-shot-iphone-11-pro-max-2020-06-24.png
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
(no solutions)
Can you please attach a small project that demonstrates this issue? Thanks!
I have the same issue only on iOS
This issue begins after update to XF 4.7

@adrielmsantos Does your DataTemplate include a Frame?
@hartez Yes. Inside a Frame
The overlapping occurs after scrolling
@samhouts
You can reproduce this issue in this xamarin forms sample: ListViewColors
Same issue here. Is happens if I create a ListView with an ItemTemplate which places a Label inside a Frame. The ListView is rendered fine but as soon as you start to scroll, the Labels start to overlap with eachother.
Same issue here. It works on XF 4.6.0.847, but all newer versions has this issue.
My DataTemplate looks like this:
<DataTemplate>
<ViewCell>
<Frame BorderColor="Gray" HasShadow="True" Margin="15,10,15,10">
<StackLayout Orientation="Horizontal" Spacing="20">
<ffimageloading:CachedImage HorizontalOptions="Start" VerticalOptions="Center"
WidthRequest="100" HeightRequest="100"
DownsampleToViewSize="true"
FadeAnimationEnabled="True"
Source = "{Binding ImageUrl}">
</ffimageloading:CachedImage>
<StackLayout Orientation="Vertical" VerticalOptions="Center" HorizontalOptions="Center" Spacing="0">
<Label Text="{Binding Title}" FontSize="Medium" FontFamily="Roboto-Bold" Margin="0,0,0,0"/>
<Label TextType="Html" Text="{Binding SubText}" FontSize="Small" TextColor="LightGray"/>
</StackLayout>
</StackLayout>
</Frame>
</ViewCell>
</DataTemplate>
If I remove the Labels text bindings, and hardcode the text, it works.

From a bisect
The merge base de38e1d79c9d1daf7668f8f566504dbeda46bdd2 is bad.
This means the bug has been fixed between de38e1d79c9d1daf7668f8f566504dbeda46bdd2 and [b4a6a7cec76e4ac255198353d726c27603fcaf72 ba337c66d06b45842d84703d77e60b032312ff66].
Is there a timeframe on a fix. Been in the wild for a month or so now. Preventing our production release
Any news? I tried 4.7.0.1142 and pre-release of 4.8.0.1143. The problem is still there. What version will it be fixed in?
Please try 4.6.0.1180 or 4.7.0.1179 or 4.8.0-pre2. Thanks!
Most helpful comment
Is there a timeframe on a fix. Been in the wild for a month or so now. Preventing our production release