Doesn't type G reliably

[tejado]

Doesn't type G reliably

[tejado]

Hi,

this sounds strange - never had any issues with the character "g". I just testet it and it worked fine for me.
On what operating system did this occur? Could you test it on a different computer and report back your findings, please?

[webtroter]

Ok. I just tested on another computer and it is the same. Both are Windows 10.

My phone is OnePlus 6, running LineageOS 18.1

[Alexander-Shukaev]

Hi, unfortunately, I have to second this. In fact, this is not particularly related to g, it's a general issue. For instance, I also noticed issues with handling of key codes dependent on the Shift modifier being pressed. For example, in certain combinations of words, if H is expected as per password, Authroizer may output h, or if : is expected as per password, Authorizer may output ;. That is it swallows Shift sometimes. Sometimes here and word "reliably" in the name of the topic might be confusing, as in fact, if the issue is there, then it is persistent with respect to a particular combination of words/letters in password, so it depends on a particular password whether the issue will be there or not and it stays like that. It currently might be a major blocker to use certain arbitrary desired passwords, one has to be very careful to come up with something that does not expose this issue.

[tejado]

Hi,
thanks for your feedback. At general this blocker should be solveable because Authorizer sends just key codes as your normal keyboard. As in my tests it worked perfectly fine, it may have something to do with your keyboard layout. What language your target system is on? Is the keyboard on the operating system configured in english or in a other language @webtroter and @Alexander-Shukaev ?
And which default language (settings -> Auto-Type Keyboard Layout) do you use in Authorizer? You can change that for a particular auto-typing if you press the button (e.g. Name, Password or Name/Pass) longer, then an popup opens where you can choose the output language.

For a further debugging step, it would be helpful if you can download the debug version (CAREFUL: this version logs passwords in cleartext, so use this only for debugging purposes -> so with test passwords), get the log of Authorizer over logcat, paste it into pastebin and show it here. Then I can check if there is some issue in the scan code output.

[webtroter]

I use Windows in English US with the Canadian French keyboard layout (Alt Gr + 2 = @), and us layout. Sent from away

…

On Mon., Jan. 3, 2022, 10:52 tjado mäcke, ***@***.***> wrote: Hi, thanks for your feedback. At general this blocker should be solveable because Authorizer sends just key codes as your normal keyboard. As in my tests it worked perfectly fine, it may have something to do with your keyboard layout. What language your target system is on? Is the keyboard on the operating system configured in english or in a other language @webtroter <https://github.com/webtroter> and @Alexander-Shukaev <https://github.com/Alexander-Shukaev> ? And which default language (settings -> Auto-Type Keyboard Layout) do you use in Authorizer? You can change that for a particular auto-typing if you press the button (e.g. Name, Password or Name/Pass) longer, then an popup opens where you can choose the output language. For a further debugging step, it would be helpful if you can download the debug version (CAREFUL: this version logs passwords in cleartext, so use this only for debugging purposes -> so with test passwords), get the log of Authorizer over logcat, paste it into pastebin and show it here. Then I can check if there is some issue in the scan code output. — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB77R6A3QSS3RQNMHAZUVBDUUHA4TANCNFSM5IMKO6JA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[tejado]

Should be fixed by #43