iOS device - Workaround for hidden password field

How this feature works

From iOS 13, Apple started hiding the password field when streaming the device screen. Because of this, when testing with iOS devices on Kobiton users:

  • Not able to use the soft keyboard on iOS device, although users can still input data to the password field by typing on the keyboard of the computer that launches Kobiton Portal.

  • Not able to see what they inputted in a password field (the asterisks are not shown, the password field just blanks even though the user types the keyboard of the computer).

We introduce the Workaround Dialog that enables users to see what they type in the iOS password field.


How to use

In manual session

During Manual sessions on iOS devices, when users tap on the password field, Kobiton will display the Workaround Dialog as below: image-20220307-094223.png

On this dialog, you can:

  • Input your password and click Submit button to enter it into the iOS device password field

  • Click on the Eye icon image-20220307-094223.png to reveal/hide the input password

  • Choose whether to input as sensitive data or not - once chosen as sensitive data, the password input would not be visible to other Organization users in the Session Details video, screenshots.image-20220307-094257.png

The input data will be appended to existing data in the field (if any). For example:

  • First, you input “Sample123” on the Workaround Dialog and Submit → Sample123 is inputted to the device password field. Then, recalling the password is "abc" instead, you then input “abc” and Submit → the value passed to the device password field will be "Sample123abc". You have to remove "Sample123" by tapping and deleting directly on the device password field.

On the Session Details

  • The data you inputted via the Workaround Dialog will be displayed on Session Details as “Type” action.
  • If you enabled “Input as sensitive data”, the password will be shown as asterisks, otherwise, the password will be shown as plain normal text data.


Was this article helpful?
0 out of 0 found this helpful