Hello,
suddenly getting below error in type into field.
Type Into ‘Password*’: The element was found but the verification failed. It could be because you are trying to type in a password field that obfuscates the typed string.
it was running proper till yetserday without any issue and today suddenly getting this error
help me to resolve.
@Mathkar_kunal
Did you updated Verify option as None? Or any other value updated? if value updated, make it as None and then try and let me know if you still facing the same issue.
Happy Automation
@Mathkar_kunal This usually happens with Modern Type Into when Verify execution is enabled.
For password fields, UiPath types the value correctly, but after typing it tries to verify the entered text. Since password fields are masked/obfuscated, UiPath cannot read the actual value back, so it throws this error.
Solution:
Under Verify execution, make ‘None’
@Mathkar_kunal Please let us know if it works
i have selected verify password is null now password is not entering and giving error directly on page as username and password is wrong -
@yedukondaluaregala @Dhruba_Jyoti_Kalita
@Mathkar_kunal
Just confirm Is that Password datatype is securestring?
If yes, can you change that secure string to string and try. to convert secrure string to string
New System.Net.NetworkCredential(string.Empty, yourSecureStringVariable).Password
after entering this expression in type into activity then you need to select the Standard option instead of secure
use debug mode before executing this activity run the above expression in immediate panel so that you can ensure that whether that variable is getting the value or not
give a try and let me know
@Mathkar_kunal From your screenshot, username is entered but password field is blank, so please check the below points:
-
In Type Into Password, you selected Secure mode.
So the value must be passed in the Secure text property, and the variable should be of type SecureString.
-
If your password variable is a normal String, then either:
-
switch the activity from Secure to Standard and pass it in Text, or
-
use a proper SecureString value from Orchestrator Credential / Windows Credential.
-
Before clicking Log in, add a small check/log:
-
Re-indicate the password field once again, because the screenshot shows the activity is linked to an element/object repository. If the target is wrong or outdated, it may not type in the password field.
-
Keep these options enabled:
deleteing the previous selector and reindicating to password field resolved the issue , only thing i have put 0.3 sec delay before