Peekable Passwords in Field Maps

[ErikTownsend]

So a constant issue we have in our userbase is people not being able to login. 95% of this is due to either and expired or incorrectly entered password. Is it possible to make passwords peekable? I know one of the goals of creating field maps is less logins. This isn't as much an issue for us since we use AD for passwords across several platforms(ESRI, outlook, windows, etc) but because of this we have robust passwords(aka difficult) that people are required to update periodically. To compound this issue, the users have to enter passwords on a tablet screen, which can increase the chance of typos.

[BrentPierce]

I like this idea we will add it to our backlog

[AndrewCroisier]

@BrentPierce One thing I've noticed in Collector Classic is that when users have a keyboard that enables suggested words, sometimes the phone recognizes their username. When they begin typing their employee ID in the keyboard, their full ID is autosuggested by the keyboard. If they tap their username, the keyboard enters it into the username field - but it also puts a space at the end of the username, because the keyboard expects them to continue typing a message.

When the users try to authenticate, they get an invalid credentials error - because the app is trying to authenticate a username with a space at the end, which doesn't exist. The users often don't know what the issue is, because it isn't obvious.

Is this the same experience in Field Maps? I don't have the exact same model of phone as these specific users, so I can't test it on my own unfortunately.

[ErikTownsend]

@AndrewCroisier I just tried that on my device, it still authenticated with a space on the end. It didnt autopoluate however so not sure the space is entered the same way.