[Android][Appium 1.3.5] Appium does not recognize non ascii char in text attribute

[ktronic80]

Hi,

since Appium 1.3.5 I have a problem with non ascii characters in the text attribute of an Android ui element.
I have the following xpath to find an element //[@text='Löschen'].
After the update to Appium 1.3.5 the test is failing with previous versions it works fine. In the Appium log I just see this
info: <-- POST /wd/hub/session/0e33042c-1e79-46c5-8d37-a33eefe7e98f/timeouts/implicit_wait 200 0.861 ms - 76 {"status":0,"value":null,"sessionId":"0e33042c-1e79-46c5-8d37-a33eefe7e98f"}
info: --> POST /wd/hub/session/0e33042c-1e79-46c5-8d37-a33eefe7e98f/element {"using":"xpath","value":"//[@text='Löschen']"}
info: [debug] Waiting up to 10000ms for condition
info: [debug] Pushing command to appium work queue: ["find",{"strategy":"xpath","selector":"//[@text='Löschen']","context":"","multiple":false}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"find","params":{"strategy":"xpath","selector":"//[@text='Löschen']","context":"","multiple":false}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: find
info: [debug] [BOOTSTRAP] [debug] Finding //*[@text='Löschen'] using XPATH with the contextId: multiple: false
info: [debug] [BOOTSTRAP] [debug] Returning result: {"value":"Could not find an element using supplied strategy. ","status":7}
info: [debug] Waited for 69ms so far

When viewing the element in the Appium inspector you can see that instead ö it shows ? and when using the xpath //*[@text='L?schen'] it finds the element.

It looks like that something is messed up with recognizing non ascii characters.

[amedvedjev]

did you try normalizer?
met same issue fixed my normalizing search text. see #4421 for details

[chenhengjie123]

I found that this issue is caused by commit use custome NodeInfoDumper and handle empty root nodes properly. It changes getRawXMLHierarchy() function to use custom dumper and that dumper would translate all non ascii char to ? in AccessibilityNodeInfoDumper's safeCharSeqToString() function.

Since this commit is just in 1.3.5-beta1 and 1.3.5, you can revert to use 1.3.4 to get through this problem.

[medy75]

Possibly same issue as mine: #4583
Any idea how to fix it? I cannot revert to 1.3.4 because of findElement issue.

[0x1mason]

We'll get this in the next release.

[0x1mason]

Another option would be to not use XPath.

[ktronic80]

Thanks. For now its ok for to me to use Appium 1.3.4. for Android.
@0x1mason Which other locator would work? Can I use name or linkText? Currently I only have the possibilty to identify the element by the text.

[0x1mason]

Got a fix for this. Will be available soon.

[0x1mason]

@ktronic80 Try find_by_name.

[0x1mason]

1.3.6 is out with the fix.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.