Entry not working Samsung S4 running Android 5.0.1

[ghost]

We have a strange problem with a Page with Entry controls on it.

On one particular flavour of device (we have two physical devices showing this problem) - Samsung S4 running Android 5.0.1 - Entry controls are not displaying input.

The text can be typed on the keyboard, and is even accepted and passed to the PageModel, but nothing appears on screen. This works fine on devices running Android 6.0.1 and 4.4.2.

We're using Grial, with our theme in App.xaml merged:

 <Application.Resources>
        <ResourceDictionary MergedWith="local:GrialLightTheme">

Versions: UXDivers.Artina.Shared 2.0.35 UXDivers.Artina.Shared.Base 2.0.43-RC (2.0.50-RC available) UXDivers.Effects 0.6.0 Xamarin.Forms 2.3.3.193

The problem occurs in our project even with a blank ContentPage with just a StackLayout and Entry on it.

Creating a basic blank Forms project with an Entry control works fine on the same devices.

[jpbrocca]

Hi @james-lavery, how are you? Can you attach a screen capture showing the problem? I am not sure I understand what you mean with:

Entry controls are not displaying input

Is that the bottom line on the Entry is not being displayed once the control gets focus?...or perhaps you mean that literally that the characters are not visible while you type?

If is the latter, then one possible reason for that could be that the text color is actually same as background color -we will need to find the reason for that-.

Can you see the caret when you type on the Entry?

Regards and thanks, JP

[ghost]

Hi JP, You can't see the caret. I've tried setting the TextColor explicitly to make sure it's not the same as the background colour.

I'll have to wait until Tuesday to get a screen shot.

Sent from my Android phone using TouchDown (www.symantec.com)

-----Original Message----- From: jpbrocca [[email protected]] Received: Thursday, 13 Apr 2017, 18:36 To: UXDivers/Grial-UI-Kit-Support [[email protected]] CC: James Lavery [[email protected]]; Mention [[email protected]] Subject: Re: [UXDivers/Grial-UI-Kit-Support] Entry not working Samsung S4 running Android 5.0.1 (#169)

Hi @james-laveryhttps://github.com/james-lavery, how are you? Can you attach a screen capture showing the problem? I am not sure I understand what you mean with:

Entry controls are not displaying input

Is that the bottom line on the Entry is not being displayed once the control gets focus?...or perhaps you mean that literally that the characters are not visible while you type?

If is the latter, then one possible reason for that could be that the text color is actually same as background color -we will need to find the reason for that-.

Can you see the caret when you type on the Entry?

Regards and thanks, JP

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/UXDivers/Grial-UI-Kit-Support/issues/169#issuecomment-293969997, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABrKHncJh-sg-QnWW9IqI-cXZq1cB7akks5rvl0fgaJpZM4M87Em.

[matthewfrost]

Has there been anymore work on this? I'm experiencing a similar issue on multiple devices running Android 5.1.1. The text does not appear until the page is navigated away from and then returned. It affects both entries and spinners

EDIT: after further investigation it seems as though the bug only appears when returning to the page using the back button in the toolbar. Using the hardware back button does not cause it

[LeoHere]

@matthewfrost couple of questions:

• Can you please test if this issue happen in the Grial Sample App (available in Google Play Store)?
• What version of Grial / Xamarin Forms are you using?
• Can you please attach a screenshot of the issue?

[matthewfrost]

@LeoHere Sorry I did not realise this was a Grails thread initially so I'm guessing it's a Xamarin problem or I'm just doing something funky and not realising. But I'm on 2.3.4.247 of Xamarin forms

[MicaNareia]

Hi! @james-lavery, @matthewfrost, by default the android app is using the holo dark theme, simply change it to Holo.Light in the AndroidManifest.xml (that's the problem)