Missing a character of string when Text Into Secure is run

Hi. when I use Type Into Secure with Hardware Events, a character of string is not input in the form.

I don’t know the reason.

How can I handle this?

In my case, the character is ‘v’.

‘v’ is not typed to a form when I enter by using Type Into Secure(Hardware Events).

Convert the same in string & use Type into

StrVar= (new System.Net.NetworkCredential(“”, mySecureString,)).Password

Hi @very

Check out this thread

Hope it helps!!

I am using Assign activity like the below

ppp = (new Net.NetworkCredential(“”, “vopo333”)).SecurePassword

and use the variable ppp in Type Into(secure, hardware events).

‘v’ in “vopo333” is missing…

Just opo333 is typed in the form.

Hi @very

Give the delay before Type Into of Password and try.

Regards

I already did, I gave enough delay(5s).

but the same thing happens.

Hi @very

Use Check App state activity and indicate the Password block. If the target appears then give Type Into activity and type the password.

or use Get password activity
image

The output variable type is also System.String

Regards

Hi @very

Can you try to use Simulate Type option

Cheers!!

Hi @very

Check by debugging the code by using BreakPoint for that activity in the immmediate Panel,Whether the variable storing the value or not.

Hope it helps!!

Hi

Can you try using SimulateType or SendWindowsMessages?

Ensure that the target application has the focus when the “Type Into Secure” activity is executed. Some applications may not capture keyboard input if they are not the active window.

@very

Try using a click activity before type into and then use type into without qctivate and click before and check if it resolves

Cheers

Sometimes, it could be that the bot is typing it too fast. Can you try the option of “Delay between keys”

Hello @very,

Sometimes, this type of situations arise that are contingent upon the behavior of the application. In such cases, it’s advisable to experiment with various property settings, such as:

  • Initially, attempt with the ‘Simulate’ type.
  • Next, try introducing a delay between keystrokes.
  • Consider using the ‘SendWindowsMessages’ option.

Typically, one of the aforementioned methods should resolve the issue.