Xamarin.forms: [XF] Entry inside Expanded View Cell not working properly

[ferbeltran]

Description

A Entry inside a Expanded ViewCell doesnt behave properly: It doesnt respond the first time you tap it, and then closes the Keyboard (Numeric) after every numeric input

Just affecting Xamarin Forms under iOS

Steps to Reproduce

1. Create a Custom ViewCell that expands upon tapping
2. Place the entry in the expanded section of the viewcell
3. When ViewCell is expanded, tap Entry

Expected Behavior

Tap the Custom ViewCell to expand and show the Entry control. Entry must show Soft Keyboard on first tap and should stay open until "Done" button is pressed

Actual Behavior

Tapping the ViewCell expands itself and shows Entry control, but Entry doesnt respond to first tap to show soft Keyboard. Upon 2nd tap it shows it but just to close after every number pressed

Basic Information

• Version with issue: Xamarin.Forms 3.2.0.839982
• Last known good version: Xamarin.Forms 3.1.0.697729
• IDE: Visual Studio 2017
• Platform Target Frameworks:
  
  
  
  • iOS: 11.0
  
  
  • Android: N/A
  
  
  • UWP: N/A
  
  
• Android Support Library Version:
• Nuget Packages:
• Affected Devices:

Screenshots

Reproduction Link

Works fine using XF 3.1
https://streamable.com/w9j12

Doesnt work using XF 3.2
It doesnt show in this video but i am tapping the entry TWICE for the Keyboard to appear
https://streamable.com/yzn3w

[hartez]

Create a Custom ViewCell that expands upon tapping

@ferbeltran

Can you provide us with some more detail on how your custom ViewCell works? If you could provide code, that would make it easier for us to diagnose this issue.

[hartez]

@ferbeltran Never mind, we've got a solid reproduction of this bug at #4067.

[taterjuice]

I am experiencing this issue on iOS both in 3.3.0.967583 and the latest prerelease, 3.4.0.987044-pre1
I can confirm the issue does not exist on Xamarin.Forms 3.1.0.697729.
Looking forward to a fix.

[james1301]

Is there any kind of workaround for this? This is making my form quite unusable and I cannot find a solution to get round it.

[tomaustin700]

We are also having this problem. This needs fixing or a workaround provided.

[JamesBrining]

This is becoming a real issue for us - please look into this ASAP

[andyr79]

Also a big issue for us too, please escalate