Is this tiny numerical keyboard "feature" part of the recent Field Maps update?

1762
15
03-03-2026 03:29 PM
_____
by
Frequent Contributor

Updated to the latest Field Maps today, and now integer fields display this tiny numerical keyboard, but it's the worst user experience ever.

When I click into an integer input, then the tiny keyboard will display for a second, but it seems like the large keyboard or the footer at the bottom tries to open too, and then they both just close. So, then I click into the input for a second time and sometimes the tiny keyboard will display fine, but other times no keyboard displays at all. So then I need to click into another input and back into it again!

This is not a good user experience at all. The tiny keyboard makes filling out the form very difficult. It also covers the inputs way too much. You can't even see what you're entering.

Is this by design? I sure hope not!

Any idea how I can disable this tiny numerical keyboard for our users?

 

IMG_0144.PNG

15 Replies
Cope31290
New Contributor

I hope its fixed soon, it is so much slower and very frustrating. I don't know how this update made it through any kind of test.

ToddJohnson
Occasional Contributor

I have also been getting complaints from many end-users. The keypad blocking the form, especially the field they are trying to modify, has been the biggest complaint. 

ShoNuff
Occasional Contributor

Thanks for bringing this up! It is very frustrating for us here.

0 Kudos
PaulBarton
Emerging Contributor

Agreed, this new keyboard for numeric entries is absolutely atrocious and has significantly slowed our data collection down. 

jameslockeocl
New Contributor

My field crews are also facing difficulty with this new feature. 

ColinLawrence
Esri Regular Contributor

I wanted to provide an update in this thread for everyone. The numerical popup added with iOS 26 will be reverted in the next Field Maps update (26.1.2) until the team can find a way to better handle how/where it appears while entering attributes. For now, the full keyboard will display again regardless of field type. 

Regards,
Colin