Bug 59006 - Focusing any Entry control inside TableView always binds to first Entry
Summary: Focusing any Entry control inside TableView always binds to first Entry
Alias: None
Product: Forms
Classification: Xamarin
Component: Android (show other bugs)
Version: 2.4.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-08-24 11:44 UTC by Jouni Suominen
Modified: 2017-10-04 18:45 UTC (History)
3 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:

Slightly modified Xamarin.Forms template project (121.86 KB, application/zip)
2017-08-24 11:44 UTC, Jouni Suominen
Additional Reproduction (1.54 MB, application/x-zip-compressed)
2017-10-04 18:38 UTC, williamd
Screen Capture of Issue (2.72 MB, video/mp4)
2017-10-04 18:39 UTC, williamd

Description Jouni Suominen 2017-08-24 11:44:11 UTC
Created attachment 24395 [details]
Slightly modified Xamarin.Forms template project

If there are for example two Entry cells inside a TableView, entering text to the first one works as expected. But if you then focus the second Entry and try to enter text to it, the text is entered to the first Entry on Android API >= 24.

Steps to reproduce:
1. Install the attached project (it's the basic Xamarin.Forms template project with modified NewItemPage.xaml)
2. Launch the EntryTest.Droid project on for example Nexus_5X_API_24_x86 (API 24) emulator.
3. Press ADD in the upper right corner.
4. Edit the "Item name" field.
5. Edit the "This is an item description" field.

Actual result: in step 5 text goes to "Item name" field.

Visual Studio for Mac Community 7.1 (build 1297).
Xamarin Forms
Android API 24
This issue does not seem to happen on API version < 24.
Comment 1 Paul DiPietro [MSFT] 2017-08-24 23:13:42 UTC
For some reasons I seem unable to reproduce this on a Galaxy S8 device which is on 7.0, nor on an API 25 emulator. Entering text into the second field as mentioned saves it accordingly (e.g. the first field being set to "one" and the second to "two" appears to work as expected) Can you confirm that the version on the reproduction is what you're using, or if anything different is possibly causing the behavior?
Comment 2 Jouni Suominen 2017-08-25 07:17:17 UTC
That's weird. One of my users reported this issue and his running Android 7.0 on HTC One X (HTC Model 10). I'm also able to reproduce this on the Nexus_5X_API_24_x86 emulator that ships with Android SDK (afaik). Would you like a screen cap video of the issue?
Comment 3 Paul DiPietro [MSFT] 2017-08-25 16:04:53 UTC
It wouldn't hurt for visual confirmation. Also, any other specific emulator configurations or devices that exhibit the behavior are good to know about as well.
Comment 4 williamd 2017-10-04 18:38:40 UTC
Created attachment 25110 [details]
Additional Reproduction

This project reproduces the issue.
Comment 5 williamd 2017-10-04 18:39:48 UTC
Created attachment 25111 [details]
Screen Capture of Issue

This example shows the bug in action on a physical Motorola Moto G4 device running Android 7.0
Comment 6 williamd 2017-10-04 18:45:33 UTC
We have a customer that primarily uses the Moto G4 and this issue is a huge blocker for us. Please see our minimum reproduction and example video above. Let me know if there is any other information I can provide.

Note You need to log in before you can comment on or make changes to this bug.