Android - Hit enter too fast and you lose the last letter of the call sign in the log

I have a cheap Fire HD 10 tablet and I’ve used both the full version and the lite version and have experienced this issue in both. I use a bluetooth keyboard and I type rather quickly and if I hit enter before it has resolved the name of the operator, it loses the last typed letter of the callsign when it saves. I’ve been able to replicate this error and it always happens if I hit enter before the QRZ api reports back.

Using my callsign as an example if I type K4ISU and hit enter as soon as I type the U (and I see it in the textbox as the full call sign) it logs K4IS.

This is only happening in the Android version. When I use my iPad Pro, or my iPhone with the external keyboard and I hit enter as soon as I finish typing the callsign (and before it resolves the operator name) it always logs the full callsign.

Note, it doesn’t do it on every entry this way. It does it 50%-75% of the time. To test, just rapid-fire enter 6 or 7 callsigns and you should be able to recreate the error.

It might be that this issue here: Features for SOTA? - #13 by OE5JFE

Is having the same origin. Looks like something with the input event handler/trigger is not working properly? Maybe if the ‘working task’ is still running the newly started (due to a change of the input field) is not triggered?