Cannot send emoji to input field with unicode keyboard

alex-k 2018-01-11 09:35:41 UTC #1

Automating tests for native android app. Trying to make Appium send emojis with sendKeys() method, but it doesn’t seem to work. I have added “unicodeKeyboard” and “resetKeyboard” to the capabilities, and logs say that keys were send, but input field stays empty.

Appium version is 1.6.5. Testing on a real device.

String I’m sending looks something like this:

private static final String GRINNING_FACE = new String(Character.toChars(0x1F601));

Telmo_Cardoso 2018-01-11 10:21:57 UTC #2

Hi,

can’t you use the java code directly instead of HEX code?

.sendKeys("\uD83D\uDE01");

alex-k 2018-01-11 10:31:50 UTC #3

Thank you for the answer. I tried to use the java code directly, but result is the same. Input field stays empty.

Telmo_Cardoso 2018-01-11 10:36:16 UTC #4

It works for me… Can you share the appium logs?

alex-k 2018-01-11 11:32:13 UTC #5

Appium logs look like this:

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type ACTION
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command action: setText
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Using element passed in: 23
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Attempting to clear using UiObject.clearText().
[HTTP] --> GET /wd/hub/status {}
[debug] [MJSONWP] Calling AppiumDriver.getStatus() with args: []
[debug] [MJSONWP] Responding to client with driver.getStatus() result: {“build”:{“version”:“1.6.5”,“revision”:null}}
[HTTP] <-- GET /wd/hub/status 200 1056 ms - 83
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Text remains after clearing, but it appears to be hint text.
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Text not cleared. Assuming remainder is hint text.
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Sending plain text to element:
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {“status”:0,“value”:true}
[debug] [AndroidBootstrap] Received command result from bootstrap
[debug] [MJSONWP] Responding to client with driver.setValue() result: true

Telmo_Cardoso 2018-01-11 11:36:00 UTC #6

Maybe you using old uiautomator… can you switch to uiautomator2?

capabilities.setCapability(MobileCapabilityType.AUTOMATION_NAME, "uiautomator2");

alex-k 2018-01-11 12:24:14 UTC #7

Yes, It may be that I’m using deprecated uiautomator.
Anyway, just tried it with uiautomator2 and got some inexplicable StaleObjectException at starting page.

Telmo_Cardoso 2018-01-11 12:25:57 UTC #8

Thats another issue Look around in the forum, there are some explanations about what it is and how to try to avoid it