It's impossible to open the single-row keyboard for entrys that have OTP additional string

[roman90sv]

When i delete additional OTP string, the problem disappears.
since v1.07-r1 (Android 8.1.0)

But, TOTP generation is working properly: https://i.imgur.com/npou3px.jpg

[dragoangel]

Mi MIX2 (MDE5), Android 8.0 (OPR1.170623.027), MIUI 10.3.1.0 (ODEMIXM)
Vote up, same issue here after upgrade to 1.07f. Any record that have OTP record can't be seleted at K2A keyboard.
Previous flow:

1. Opened app/browser with login screen
2. Switch to Keepass2Android, open needed record and my keyboard aumotically switch to one-line keyboard
3. Switched back to my app with login screen and proceed login with selected record accesible throu one-line keyboard.

After upgrade (apply only for records with OTP keys):

1. Opened app/browser with login screen
2. Switch to Keepass2Android, open needed record and my keyboard aumotically switch to one-line keyboard
3. Switched back to my app with login screen and K2A keyboard have no selected record at all
4. Use select option button to open K2A
5. Select needed record and automatically return to app/browser
6. Still K2A keyboard have no selected record at all 😑

[dragoangel]

I'm now downgraded to https://github.com/PhilippC/keepass2android/releases/tag/1.06f and all work fine. Will wait for 1.08f version with bugfix

[roman90sv]

dragoangel
Я еще заметил, что на старом андроид 4.4 диалог смены клавиатуры всегда открывается автоматически после успешного поиска записи по url из браузера. Но на 10м MIUI (redmi note 5) диалог почти на всех сайтах не открывается. Приходится вручную вызывать диалог (долгий там по пробелу). Проблему можно решить плагином Keyboardswap, который сам переключает клаву на кипас, но для него требуется через режим отладки присвоить android.permission.WRITE_SECURE_SETTINGS, а для этого в свою очередь требуется зарегистрировать micloud и залогинить смартфон (иначе миюай не позволяет через консоль раздавать права приложениям). Такие вот дела. И еще раздражает, что плагин оставляет свое окошко в интерфейсе недавних приложений.

[dragoangel]

@roman90sv
I'm always use KeyboardSwap App so I'm not see any issue 😅. It align my base requirements in configuration of my phone. Due I have MiAccount I from old times, I even doesn't know that such custom ADB-launched permission not working without it 😆.

[dragoangel]

Good morning GPlay autoupdated my K2A. This such a pain. After dawngrade need to disable autoupgrade for k2a in GP.

[JohnLGalt]

I am experiencing the same behavior as dragoAngel has listed below, and it has been happening with the 1.07 releases, even when I was a ßeta tester, to the point where I left the ßeta program to revert to 1.06 stable version.

Now Google Play store has updated me to version 1.07-r1 and I'm experiencing the same issue again. Please move 1.07 back to ßeta status until this issue can be resolved.

It is 100% reproducible with 1.07-r1 and never occurs with 1.06f.

Mi MIX2 (MDE5), Android 8.0 (OPR1.170623.027), MIUI 10.3.1.0 (ODEMIXM)
Vote up, same issue here after upgrade to 1.07f. Any record that have OTP record can't be seleted at K2A keyboard.
Previous flow:

1. Opened app/browser with login screen

2. Switch to Keepass2Android, open needed record and my keyboard aumotically switch to one-line  keyboard

3. Switched back to my app with login screen and proceed login with selected record accesible throu one-line keyboard.

After upgrade (apply only for records with OTP keys):

1. Opened app/browser with login screen

2. Switch to Keepass2Android, open needed record and my keyboard aumotically switch to one-line  keyboard

3. Switched back to my app with login screen and K2A keyboard have no selected record at all

4. Use select option button to open K2A

5. Select needed record and automatically return to app/browser

6. Still K2A keyboard have no selected record at all 😑

[theolike]

I reported and commented on this several different times before the Google+ page shutdown. I had to leave the beta program because it kept popping up. I wouldn't mind coming back. I'm generally tolerant of errors, but this is such a key feature for me I couldn't wait any longer. Now that it's been pushed to the stable branch I really hope it will get fixed.

[JohnLGalt]

Indeed - When I realized it was the ẞeta build of 1.07 I opted out of the ẞeta program as well.

But now 1.07-r1 is being pushed as stable by Google Play. So, I opted to do as dragoangel mentioned - manually install 1.06f, and then going into Google Play, selecting K2A and disabling automatic updates.

Play store still mentions that the update is available, but it won't automatically update, and you can just skip it when updating other stuff if you need to manually update other apps.

[torerikk]

I'm also seeing this problem on my Pixel 3. The problem went away for a few days after wiping the app's storage.

[tiberius8]

I'm also experiencing this is. Only affects entries with totp.

[p0wertiger]

Subscribing, affects me as well. For me this is related to having TOTP set up in the entry, works fine when the entry has only password configured.

[JohnLGalt]

I'll double check - I have several entries that have more than just opt keys as entries in the advanced tab - not sure if it is only otp or anything at all in the advanced fields.