This behaviour is a side effect of Maestro's anti-flakiness behaviour. Maestro expects that there will be a change in view hierarchy after the tap and, if there is none, it tries to tap again.
To work around this behaviour, use retryTapIfNoChange flag on your tapOn command:
- tapOn:
text: "Something"
retryTapIfNoChange: false
Text input is not supported for unicode
Unfortunately, Maestro does not yet support inputText commands that have unicode characters in them (follow this GitHub issue for status updates). Only ASCII characters are supported