Closed chauhaidang closed 1 year ago
This is apparently how tesseract recognizes that character. The only thing I can recommend is to fiddle with the various tesseract settings to see if you can get it to work better. Perhaps not downsampling the screen would mean there's enough pixels for tesseract to better differentiate between 'g' and 'q'.
At any rate, there's nothing the plugin can do to help here.
For some reason, the "q" letter on the screen is being detect as "g" and returned back from getOcrText command http request.
Appium inspector capture:
Response from getOcrText
Appium server log