Xamarin.forms: [Bug][iOS] Keyboard hides CollectionView elements

[lobbo232]

Description

When the keyboard opens it covers any elements at the end of a CollectionView. This means if you have Entrys or Editors in a CollectionView you can not see what you are typing when at the end of the CollectionView.

Steps to Reproduce

1. Create a new Xamarin.Forms project
2. Add a CollectionView to the MainPage content
3. Set the ItemsSource to a collection of items
4. Add a DataTemplate containing an Editor or Entry
5. Run the app, scroll to the end and try typing in the final item. The keyboard will open and cover the input.

Expected Behavior

The CollectionView should scroll up to show where you are typing (as it does on Android).

Actual Behavior

The keyboard covers the input on the CollectionView so you can not see what you are typing.

Basic Information

• Version with issue: at least 4.3.0.908675 and later
• Last known good version: Unknown
• IDE: Visual Studio 2019
• Platform Target Frameworks:
  
  
  
  • iOS: 13.10.0.17
  
  
  • Android: 10.1.3.7
  
  
• Android Support Library Version:
• Nuget Packages:
• Affected Devices: iOS

Screenshots

Reproduction Link

Test Keyboard hiding collection view.zip

Workaround

You can put the CollectionView in a ScrollView, however it wont auto-scroll up to focus the input. When the keyboard opens and you have to scroll up manually. I am unsure of any adverse effects of having nested scroll controls.

[jsuarezruiz]

Could be the same as https://github.com/xamarin/Xamarin.Forms/issues/9706

[FIELDPOINT]

Any chance of this getting prioritized? We are receiving lots of complaints from our customers for this exact same problem.

[lobbo232]

Any chance of this getting prioritized? We are receiving lots of complaints from our customers for this exact same problem.

Last time I spoke to Xamarin support they suggested it was best to change to a ListView instead for live environments to give the CollectionView a little more time in the oven!

[lafritay]

@lobbo232 Did you ever figure out a workaround for this?