Yubikey OTP via NFC does not work anymore

[lubobde]

The database does not open anymore with yubikey neo, OTP NFC.

All that happens is a short flickr of the screen and that's it. No error message, master password and OTP numbers still visible on the screen.

On desktop all works fine, database and yubikey are ok.

K2A Version 1.07-r1, Android 9 on Moto Z2 Force

[chrimez]

Same here: Yubikey OTP does not work anymore
UPDATE: my problem below turned out to be a sync issue of otp-file between my on premise and cloud copies.

---

It's always been working as a charm - Thank you Philipp!
After a while not using the Android client for kdbx access, I tried to open in mid September: without success. Error when entering Pwd and OTP (via NFC):

Fehler beim Erstellen des OTP Schlüssels. Bitte stelle sicher... die richtigen OTPs verwendet hast.

I checked many times: OTPs are correct. Also, they work with Win10 client.

my Software changes in meantime (afaik):

• Android: major OS 'Pie' update Samsung OTA
• Win10: upgrade to KeePass 2.4.1 (from ca. 2.3.9)
• Win10: upgrade to OtpKeyProv 2.6
• Think no updates available / changes to K2A in the same time....

Android: K2A 1.07-r1, Android 9 on Samsung S8 SM-G950F (on latest official Samsung 2019-Aug OTA Android Pie)

[Johlar76]

Have the same problem on my Samsung S10. Had an S9 before with the same problem and I was hoping it would work better with the S10, but NO. Not exactly the same behavior, but the result is the same.

When I'm trying to read the first OTP in K2A with NFC, I'm kicked back to the phones homescreen. Seems like the Yubikey payload is misunderstood by K2A. When I'm loading the OTP via USB, both to PC or phone (via OTG adapter), it works fine, but not over NFC.

K2A version 1.07-r1, Android 9 on Samsung S10 SMG973F

[yangsheng6810]

Sorry I am actually using Challenge-Response instead of OTP. I am keeping the original post as follows in case it is related.
------------ Original Post -------

Same problem here, with a OnePlus 5t and Yubikey 5 (NFC).
I have KeePassXC (on Arch Linux and Windows), and Yubikey OTP works on both platform. I am able to use OTP via OTG adapter on my phone too. However, for NFC, I get "YubikeyChallange failed, YubikeyChallange canceled".
K2A version 1.07b-r0, Android 9 on OnePlus 5T A5010 (security patch Oct 2019).

[tilllt]

Same here. Doesnt work over NFC, works fine with USB. Is there some kind of fix in the works? This is really a showstopper for me using Keepass2Android, since i cant open my safe without the Challenge-Response from the YubiKey.
Are there alternatives to Keepass2Android that support Challenge Response over NFC and work?

Oneplus 5t // OxygenOS 9.0.10 // keepass2android 1.08-pre3

[tilllt]

Ok the solution (for me) was pretty easy: Just change the Database Format to KDBX 4 in the Security Settings of KeepassXC 2.5.3 ...

Relevant: pp3345/ykDroid#7 (comment)