NFC re-triggers after authentication

[erayd]

Bug description

When using an NFC card to authenticate (in my case, Yubikey Neo), NFC immediately re-triggers as soon as authentication completes. TermBot appears to intercept the request - so nothing else actually happens - but the device does vibrate again.

This happens only with NFC; there doesn't appear to be any issue when using the same token via the USB port.

Steps to reproduce

1. Open new session to host
2. Enter PIN
3. Hold token to back of phone
4. Notice extra vibration / NFC trigger after auth completes

Expected behavior

NFC should not re-trigger until after the token has been removed.

Android device

• Device: Samsung SM-G973F (Galaxy S10)
• OS: Android Pie 9.0
• ConnectBot Version: 1.9.5-67-0366e35-termbot (installed from Play Store)

Server information

Not relevant; the problem occurs with all available server implementations.

[dschuermann]

Ah yup, I see. I suspect the cause. Will fix this.

[dschuermann]

I just released a new version on Google Play. This issue should be fixed now.

Please report back. If the issue still exist, we can re-open the bug report.

[erayd]

Thank you. Unfortunately, this issue still appears to be present; the version currently on Google Play still re-triggers immediately after authentication completes.

[erayd]

Can confirm that this is still an issue. Latest version of Termbot, on Android 11 (Galaxy S10).

[arnowelzel]

Same here, Termbot 1.9.6-151-464c55c-termbot in Google Pixel 6a with Android 13.

Using NFC for authentication is not possible and after restarting Termbot, it will not even offer to use NFC any longer.