Hi
I have a weird thing started happening with the number bar. If I start to enter a 2E0 call sign, 2 number 2’s appear. It works as you expect using the IOS keypad numbers.
Thinking it maybe a problem with my IPad mini, I checked and the same happens on my iPad.
The operation is SOTA.
Both devices running IOS 18.4.1 with HAM2K April 25 patch 6.1
73
Paul MW0PDV
Additional information, to replicate the problem I have to enter a 2 in the call field using the number bar, delete the number 2 with back space. Then when entering 2 using the number I get a duplicate 2.
If I close the operation and then reopen it seems to reset the problem until you delete a number using back space.
Paul
I came here to report a similar glitch - with the number bar visible (iPhone, PoLo 25.4.7) when I type a digit using the number bar in an RST field, I get doubling of the digits (press ‘5’ and get ’55).
More testing reveals something interesting: I enter the Call field and enter AA0A (using 0 in the number bar). So far so good. Now backspace to remove the call and press ‘2’: I get ‘2A’. Backspace and enter ‘N0̸MII’, backspace to clear, type ‘3’ and get ‘3N’. Seems the first field char that was entered (and then cleared) is hanging around to tag onto a number bar digit when it’s entered.
And that’s what’s happening in the RST fields too. It’s not a “double” of the number when it’s pressed… it’s the number that’s pressed, followed by the phantom “last number that was here being added to what you pressed.”
Hope that helps!
bug-report
That’s very helpful. I’ll try to get to the bottom of this.
I never enter RSTs but how does the shortcut entry mechanism interplay with this behaviour?
Alan
It’s a little maddening until you realize what’s going on 
Until it’s fixed, just use the “normal” number row rather than the number bar. If you’re in an RST field, the regular number row will be visible. Use those instead of the number bar.
I suggest keeping the “numbers row” feature on because it makes it easy when entering call signs. Well… most call signs… if a DX call starts with a digit you will experience the problem. In this case you’ll need to tap the “123” key to bring up the keyboard’s normal number row so you can enter that first leading digit.
Again… all the above is workaround until the problem is fixed.
Yes, please keep this number bar since it is useful to have the numbers available at only one finger tip.
Vy 73, Markus