Mobile Android login fails with complex password

Steve Hiner

I've been fighting with the mobile version this evening (which I haven't used in years). I was unable to login. I reset my password and was able to login in the browser but was still unable to login on mobile. My phone is running Android 11 so I believe it's a supported version. 

I finally decided to try changing my password to something simpler and then I was immediately able to login on mobile. My password was around 20 characters and fairly complex with numerous symbols and it seems that failed on Android.

Just a tip for anyone like me that is having trouble logging in. I know it's the worst advice to give but try making a simper password, or at least change how your password is made complex, maybe try different symbols. When creating the password it did not warn me about using invalid characters so I'm not sure if they are recognized as not being allowed on Android. 

The mobile app should be tested for all sets of symbols to make sure anything allowed in the browser is also allowed on mobile.

Steve Hiner

I confirmed I was able to create a complex password that still works on mobile but I had to drop { and/or } from the password.

Robert M. Warren

Hi Steve. Welcome to the user forums.

The mobile app should be tested.....

Indeed. I would also add the following, in case Logos personnel read this. These observations are from the perspective of an old man who is going blind, but I think they would help everyone. They would be most helpful on mobile, but wouldn't hurt for all platforms.

• Provide a 'Show Password' button. (This might have made Steve's evaluation of his complex password more practicable.) After all, this is not about nuclear launch codes. Many of my most sensitive financial websites provide this.
• Provide 'lowest-common-denominator' styling for login dialogs, meaning: Assume accessibility needs at login. Fields and text boxes should be large, vivid, high-contrast, pure black-on-white (or reverse) with NO grayscale or italic fonts and NO gray backgrounds. If anyone's artistic sensibilities are bruised during login, they'll get over it soon enough.
• The login response shouldn't 'fib' to the user and report 'invalid login', etc., when there's a different problem, such as 'unsupported OS'.
• Lose (or don't implement) hellish CAPTCHA rountines. (See first bullet re: launch codes.)