Verified this issue with Visual Studio 17.10.0 Preview 4 (8.0.7 & 8.0.20).I can repro this issue

I have noticed a small issue similar to this but on android, it only happens when I navigate backwards from a frame in the carousel view. Going from Frame 5 -> Frame 4 will cause portion of the carousel to render incorrectly. If I continue to swipe all the way back to frame 1 and go back to Frame 4 the view renders fine, again go to Frame 5 -> Frame 4 and I will see the issue again.

No issue when doing this on iOS.

Our MAUI app's main feature has a very prominent use of the CarouselView control and we ran into this issue in the process of converting our app from Xamarin to MAUI, so finding a solution or work around has been a high priority item for us.

I did some investigation and came up with one minimal example where the carousel worked perfectly. However, I then pulled down this repro repo and was able to replicate the issue. After comparing the two instances of the CarouselView I noticed that the example that worked did not use any data binding for the UI components while the repro example exclusively uses data binding for the image source.

This lead me to believe that it is specifically an issue with the BindingContext of the off-screen left item not getting set properly when the views are cycled. We were able to create a work around by overriding the OnBindingContextChanged method of the top level layout of the item template for our CarouselView, saving a cached instance of the previously set not-null model, and, within the same method if the BindingContext would be set to null, then instead set it to the cached model.

Also, I forked the repro example repo and added some text on top of the picture as a proof of concept.

Hope this helps!

Forked repo: https://github.com/dfausz-ebsco/Maui8_0_20_iOS_CarouselViewIssueRepro

Good catch @dfausz-ebsco seems it was with this change #14619

Unfortunately, the proposed PR needs a bit more review so this isn't going to make it for SR5