Android Portal App Can't Logon

[DaKevster]

Brand new Envisalink v4 person here, Connected to a Vista20P, and just got Envisalink all connected and working yesterday. I can logon from desktop PC to the EyezON web portal, I can also logon successfully from Android through web browser. Then I tried installing the Android EyezON app, and I cannot logon using same credentials that work on EyezON web portal. I get a "Wrong Credentials! Please try again".

I am using a long complex password, 20 chars including letters, numbers, and symbols. Is there some password limitation with the Android App? I was looking forward to the Android app and push notifications. Anyone have any ideas why can't authenticate on web but not Android App?

[GrandWizard]

Yes, there have been reports of people with passwords that use some of the special reserved characters ([;:/"'~ etc do not work. There is an open bug report for it.

Switch to a password with just alpha characters and it should work. Some special characters are allowed like !@#$%^& and that's not me swearing

[njace82]

I noticed that once you are logged into the mobile portal app, you cannot log out. Am I missing something? I would like to log out for security reasons.

[GrandWizard]

You can log all users out from your Eyezon portal under "account settings".

[njace82]

I believe you mean the web portal. I see no option in the mobile web app.

[GrandWizard]

I believe you mean the web portal. I see no option in the mobile web app.

It is on the normal web portal. There's no point in having it on the app if you lose your phone.

[championstrength]

Thanks to everyone who contributed to this thread, it was helpful. For anyone else who comes along after me, I had this same error; "Wrong Credentials! Please try again" on the Android app in late 2018, and ended up removing all special characters from my Eyez-On password, including !$&, etc.

After that, I was able to log into both the app and the web portal successfully. It may have been only one of those special characters that was the problem, but I didn't take the time to track down which of them it may have been.