Enrollment PIN

JD
John Doe
Eisen Karl GmbH

Hello Guys,

has anyone encountered a Bug where you have to enter the Enrollment PIN exactly 2 Times?

When i start the Agent i get a prompt for password, i then need to enable keyboard ( only numberfield on CN51). After that ill type in the PIN and i tested this multiple times, so PIN was 1000% correct, but after entering screen goes back to the "Enther Enrollment PIN".

Entering the PIN again is then succesful..

 

Agent(A+): 13.6.0.1045

MobiVersion: 14.2.2.1170

Thanks in Advance.

6 years ago
Android
ANSWERS
R
RKMOD@SOTI
6 years ago (edited 6 years ago)

Hi John,

We don’t have any such bug reported as of now. Could you please provide the following details?

  • What is the OS of the device you’re using?
  • Have you verified the behavior with the latest agent version v13.7?
  • Do you face the same issue with QR code enrollment?
  • Do you have to perform the QR code enrollment twice?

Please feel free to let us know for any of your queries.

JD
John Doe
6 years ago

I have done further testing and it looks like the "enable Hardware keyboard" (Touchscreen Keyboard) is the reason.

When i scan the enrollment pin there is no problem at all.

I guess this is a Honeywell-Problem or can anyone test this on another device, whilst enabling touchkeyboard?

R
RKMOD@SOTI
6 years ago (edited 6 years ago)

Hi John,

Thank you for your reply.

If you would like to get this issue properly investigated, I would recommend opening a Support case here so that a technical engineer can further verify if there are any other factors leading to this behavior.
 
Please let me know if any more information is required.

JD
John Doe
6 years ago

Hi,

just to give a little update.

I tested this with the new agent 13.7 and the problem still occurs.

I didnt have the time yet to look into this further with adb logs and will report back if i have any further information, this is probably a honeywell problem as it happens when you activate touchkeyboard.

JD
John Doe
6 years ago

Hello @All,

under Version 14.42 with Agent 13.9 the issue was resolved or you could say its not happening anymore.

Just as Info.