TextBox doesn't seem to receive the typed characters on Android. This works on iOS, Standalone and in the player.

example:

<Viewbox Stretch="Uniform">
<TextBox Background="White" FontSize="66"/>
</Viewbox>

It seems that when virtual keyboard is shown, text box is losing the focus.
I fixed the code and will be solved for the next release.
If you are interested I can send you a patch so you can test it.

?

Answer corrected...

great!

and yes, please send me the patch!

The patch you sent me seems to work great!
Only one small problem remaining on iOS: if the keyboard is hidden using the "hide keyboard"-key on the keyboard, the focus of the TextBox will still be lost.

a million thanks for the quick fix!

Hi!

We incorporated that patch in v1.1.2 but we couldn't dedicate more time to the rest of the issues. Reading this post and others I think we have still two things pending:

Only one small problem remaining on iOS: if the keyboard is hidden using the "hide keyboard"-key on the keyboard

Are you sure this is iOS and not Android? I can't find the hide keyboard key in the current iPhone I have in front of me right now.

also, more a cosmetic issue... on iOS, the buttons on the inputbox attached to the keyboard ("Done", "Cancel") are not localized. they display in english regardless of the system language.

Those buttons are managed by Unity itself. You can override the virtual keyboard NoesisGUI is showing by using NoesisGUISystem.OverrideDefaultSoftwareKeyboardCallbacks() function (that by the way is not documented. Will be added in the next version)

Only one small problem remaining on iOS: if the keyboard is hidden using the "hide keyboard"-key on the keyboard

Are you sure this is iOS and not Android? I can't find the hide keyboard key in the current iPhone I have in front of me right now.

sorry, i didn't mention that i was talking about iPad. iPad has that key, but iPhone doesn't.

unfortunately, we have to wait until next week to try 1.1.2, but we're very much looking forward to it!

keep up the good work!

yes, I have been able to repro the problem in the iPad.

Added to the list of things to be fixed!