github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #350] Login resets to beginning or crashes on Yubikey/keyboard plug in/out at 2FA screen #48711

New Issue
Closed
opened 2026-05-01 06:14:28 -05:00 by GiteaMirror · 26 comments
GiteaMirror commented 2026-05-01 06:14:28 -05:00
Owner
Copy Link

Originally created by @bradfa on GitHub (Jul 31, 2018).
Original GitHub issue: https://github.com/bitwarden/android/issues/350

Originally assigned to: @eliykat on GitHub.

When trying to log in on Android, when plugging in a Yubikey or a standard keyboard via USB as a 2FA device at the 2FA screen, the app will return to the beginning of the login process or crash entirely. This makes using a Yubikey via USB impossible unless you insert it prior to opening the Bitwarden app to start the login process.

The app appears to crash if I wipe all the app's data from the device and then try to log in, plugging my Yubikey in at the 2FA screen. The app appears to go back to the start page of the login process when plugging my Yubikey in at the 2FA screen if I've already once successfully logged in. I'm unsure why there's a difference here, cached or saved data locally matters?

My testing has been on an LG G5 model RS988 running Android 7.0, a Yubikey NEO via USB, and Bitwarden version 1.17.1 from the Play store.

Originally created by @bradfa on GitHub (Jul 31, 2018). Original GitHub issue: https://github.com/bitwarden/android/issues/350 Originally assigned to: @eliykat on GitHub. When trying to log in on Android, when plugging in a Yubikey or a standard keyboard via USB as a 2FA device at the 2FA screen, the app will return to the beginning of the login process or crash entirely. This makes using a Yubikey via USB impossible unless you insert it prior to opening the Bitwarden app to start the login process. The app appears to crash if I wipe all the app's data from the device and then try to log in, plugging my Yubikey in at the 2FA screen. The app appears to go back to the start page of the login process when plugging my Yubikey in at the 2FA screen if I've already once successfully logged in. I'm unsure why there's a difference here, cached or saved data locally matters? My testing has been on an LG G5 model RS988 running Android 7.0, a Yubikey NEO via USB, and Bitwarden version 1.17.1 from the Play store.
GiteaMirror commented 2026-05-01 06:14:34 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Unfortunately I don't have an Android device with a USB port on it at this time, so I can't reproduce the issue. I'll see if there is anything in the crash logs.

<!-- gh-comment-id:409323514 --> @kspearrin commented on GitHub (Jul 31, 2018): Unfortunately I don't have an Android device with a USB port on it at this time, so I can't reproduce the issue. I'll see if there is anything in the crash logs.
GiteaMirror commented 2026-05-01 06:14:35 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Could you give me an approx timestamp on a crash (make sure you open the app again after the crash so that the report can be uploaded)?

<!-- gh-comment-id:409324223 --> @kspearrin commented on GitHub (Jul 31, 2018): Could you give me an approx timestamp on a crash (make sure you open the app again after the crash so that the report can be uploaded)?
GiteaMirror commented 2026-05-01 06:14:36 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

@kspearrin I reproduced it while writing up this issue, so some time just prior to 12:54pm EDT today was when I experienced the "crashes" (in quotes because the app exited but I'm not entirely sure why, it seemed like a crash to me).
In testing right now, I'm now unable to reproduce the crash but I still can reproduce the "return to the beginning of the login process" failure mode.

<!-- gh-comment-id:409331383 --> @bradfa commented on GitHub (Jul 31, 2018): @kspearrin I reproduced it while writing up this issue, so some time just prior to 12:54pm EDT today was when I experienced the "crashes" (in quotes because the app exited but I'm not entirely sure why, it seemed like a crash to me). In testing right now, I'm now unable to reproduce the crash but I still can reproduce the "return to the beginning of the login process" failure mode.
GiteaMirror commented 2026-05-01 06:14:37 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

@kspearrin just had it crash again just now, 3pm EDT.

<!-- gh-comment-id:409331721 --> @bradfa commented on GitHub (Jul 31, 2018): @kspearrin just had it crash again just now, 3pm EDT.
GiteaMirror commented 2026-05-01 06:14:37 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Ok, thanks. I found the crash log:

Xamarin caused by: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Java.Lang.IllegalStateException: Foreground dispatch can only be enabled when your activity is resumed
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 
  at Java.Interop.JniEnvironment+InstanceMethods.CallVoidMethod (Java.Interop.JniObjectReference instance, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x00069] in <fd47eb562139466c9c630be6613ec122>:0 
  at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeAbstractVoidMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x00014] in <fd47eb562139466c9c630be6613ec122>:0 
  at Android.Nfc.NfcAdapter.EnableForegroundDispatch (Android.App.Activity activity, Android.App.PendingIntent intent, Android.Content.IntentFilter[] filters, System.String[][] techLists) [0x0008e] in <528ad9ae001340cd9cd464d42d836a06>:0 
  at Bit.Android.MainActivity.ListenYubiKey (System.Boolean listen) [0x00068] in <add3e379c4594eac8d5b6b8d5461e2e8>:0 
  at Bit.Android.MainActivity.<OnCreate>b__7_0 (Xamarin.Forms.Application sender, System.Boolean listen) [0x00000] in <add3e379c4594eac8d5b6b8d5461e2e8>:0 
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00032] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 
   --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0004b] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 
  at Xamarin.Forms.MessagingCenter+Subscription.InvokeCallback (System.Object sender, System.Object args) [0x00076] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 
  at Xamarin.Forms.MessagingCenter.InnerSend (System.String message, System.Type senderType, System.Type argType, System.Object sender, System.Object args) [0x0006b] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 
  at Xamarin.Forms.MessagingCenter.Xamarin.Forms.IMessagingCenter.Send[TSender,TArgs] (TSender sender, System.String message, TArgs args) [0x00013] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 
  at Xamarin.Forms.MessagingCenter.Send[TSender,TArgs] (TSender sender, System.String message, TArgs args) [0x00005] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 
  at Bit.App.Pages.LoginTwoFactorPage.ListenYubiKey (System.Boolean listen, System.Boolean overrideCheck) [0x00026] in <c121207d583c4169bad14f6f352eb197>:0 
  at Bit.App.Pages.LoginTwoFactorPage.OnAppearing () [0x00006] in <c121207d583c4169bad14f6f352eb197>:0 
  at Xamarin.Forms.Page.SendAppearing () [0x00024] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 
  at Xamarin.Forms.Platform.Android.AppCompat.FragmentContainer.set_UserVisibleHint (System.Boolean value) [0x0004a] in <aae4e9ce5a5b4d3eaec4edf21079f3fa>:0 
  at Xamarin.Forms.Platform.Android.AppCompat.NavigationPageRenderer+<>c__DisplayClass62_0.<SwitchContentAsync>b__0 () [0x0000d] in <aae4e9ce5a5b4d3eaec4edf21079f3fa>:0 
  at Xamarin.Forms.Forms+AndroidPlatformServices+<>c__DisplayClass23_0.<StartTimer>b__0 () [0x00000] in <aae4e9ce5a5b4d3eaec4edf21079f3fa>:0 
  at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <528ad9ae001340cd9cd464d42d836a06>:0 
  at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <528ad9ae001340cd9cd464d42d836a06>:0 
  at (wrapper dynamic-method) System.Object.bc1ed743-3c60-418f-b831-1c9301b37169(intptr,intptr)
	at mono.java.lang.RunnableImplementor.n_run(Native Method)
	at mono.java.lang.RunnableImplementor.run(RunnableImplementor.java:30)
	at android.os.Handler.handleCallback(Handler.java:751)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6247)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762)
<!-- gh-comment-id:409332387 --> @kspearrin commented on GitHub (Jul 31, 2018): Ok, thanks. I found the crash log: ``` Xamarin caused by: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Java.Lang.IllegalStateException: Foreground dispatch can only be enabled when your activity is resumed at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 at Java.Interop.JniEnvironment+InstanceMethods.CallVoidMethod (Java.Interop.JniObjectReference instance, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x00069] in <fd47eb562139466c9c630be6613ec122>:0 at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeAbstractVoidMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x00014] in <fd47eb562139466c9c630be6613ec122>:0 at Android.Nfc.NfcAdapter.EnableForegroundDispatch (Android.App.Activity activity, Android.App.PendingIntent intent, Android.Content.IntentFilter[] filters, System.String[][] techLists) [0x0008e] in <528ad9ae001340cd9cd464d42d836a06>:0 at Bit.Android.MainActivity.ListenYubiKey (System.Boolean listen) [0x00068] in <add3e379c4594eac8d5b6b8d5461e2e8>:0 at Bit.Android.MainActivity.<OnCreate>b__7_0 (Xamarin.Forms.Application sender, System.Boolean listen) [0x00000] in <add3e379c4594eac8d5b6b8d5461e2e8>:0 at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00032] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 --- End of inner exception stack trace --- at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0004b] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in <e44be0cdd50d455da1e7c0f6bc4979bf>:0 at Xamarin.Forms.MessagingCenter+Subscription.InvokeCallback (System.Object sender, System.Object args) [0x00076] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 at Xamarin.Forms.MessagingCenter.InnerSend (System.String message, System.Type senderType, System.Type argType, System.Object sender, System.Object args) [0x0006b] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 at Xamarin.Forms.MessagingCenter.Xamarin.Forms.IMessagingCenter.Send[TSender,TArgs] (TSender sender, System.String message, TArgs args) [0x00013] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 at Xamarin.Forms.MessagingCenter.Send[TSender,TArgs] (TSender sender, System.String message, TArgs args) [0x00005] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 at Bit.App.Pages.LoginTwoFactorPage.ListenYubiKey (System.Boolean listen, System.Boolean overrideCheck) [0x00026] in <c121207d583c4169bad14f6f352eb197>:0 at Bit.App.Pages.LoginTwoFactorPage.OnAppearing () [0x00006] in <c121207d583c4169bad14f6f352eb197>:0 at Xamarin.Forms.Page.SendAppearing () [0x00024] in <1aabc0fecdaa41b6a5c04760c77bb648>:0 at Xamarin.Forms.Platform.Android.AppCompat.FragmentContainer.set_UserVisibleHint (System.Boolean value) [0x0004a] in <aae4e9ce5a5b4d3eaec4edf21079f3fa>:0 at Xamarin.Forms.Platform.Android.AppCompat.NavigationPageRenderer+<>c__DisplayClass62_0.<SwitchContentAsync>b__0 () [0x0000d] in <aae4e9ce5a5b4d3eaec4edf21079f3fa>:0 at Xamarin.Forms.Forms+AndroidPlatformServices+<>c__DisplayClass23_0.<StartTimer>b__0 () [0x00000] in <aae4e9ce5a5b4d3eaec4edf21079f3fa>:0 at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <528ad9ae001340cd9cd464d42d836a06>:0 at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <528ad9ae001340cd9cd464d42d836a06>:0 at (wrapper dynamic-method) System.Object.bc1ed743-3c60-418f-b831-1c9301b37169(intptr,intptr) at mono.java.lang.RunnableImplementor.n_run(Native Method) at mono.java.lang.RunnableImplementor.run(RunnableImplementor.java:30) at android.os.Handler.handleCallback(Handler.java:751) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6247) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762) ```
GiteaMirror commented 2026-05-01 06:14:39 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Does this device have NFC enabled?

<!-- gh-comment-id:409332866 --> @kspearrin commented on GitHub (Jul 31, 2018): Does this device have NFC enabled?
GiteaMirror commented 2026-05-01 06:14:40 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

In the 3pm crash yes. In the earlier crashes I'm not sure if I had NFC on
or not.

<!-- gh-comment-id:409335071 --> @bradfa commented on GitHub (Jul 31, 2018): In the 3pm crash yes. In the earlier crashes I'm not sure if I had NFC on or not. >
GiteaMirror commented 2026-05-01 06:14:41 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Can you try disabling NFC on the device completely and see if you can reproduce the crash when that off?

<!-- gh-comment-id:409335776 --> @kspearrin commented on GitHub (Jul 31, 2018): Can you try disabling NFC on the device completely and see if you can reproduce the crash when that off?
GiteaMirror commented 2026-05-01 06:14:42 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

If I disable NFC I can't get the crash to happen. With NFC disabled when I insert a USB keyboard or Yubikey during the 2FA entry page it just takes me back to the login start page.

With NFC enabled, I created the crash by inserting a USB Yubikey at 3:31 pm EDT. I then reopened the app and logged in, so hopefully you can find the crash report. It seems that NFC being enabled is required to make the crash happen.

<!-- gh-comment-id:409341095 --> @bradfa commented on GitHub (Jul 31, 2018): If I disable NFC I can't get the crash to happen. With NFC disabled when I insert a USB keyboard or Yubikey during the 2FA entry page it just takes me back to the login start page. With NFC enabled, I created the crash by inserting a USB Yubikey at 3:31 pm EDT. I then reopened the app and logged in, so hopefully you can find the crash report. It seems that NFC being enabled is required to make the crash happen.
GiteaMirror commented 2026-05-01 06:14:43 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Ok, I think the keyboard keys that the yubikey is simulating is causing the "back button" event to happen. This is why you get taken back to the login page. This is also causing it to crash when NFC is enabled because the NFC adapter/listener is not properly disconnected on back button events.

<!-- gh-comment-id:409341710 --> @kspearrin commented on GitHub (Jul 31, 2018): Ok, I think the keyboard keys that the yubikey is simulating is causing the "back button" event to happen. This is why you get taken back to the login page. This is also causing it to crash when NFC is enabled because the NFC adapter/listener is not properly disconnected on back button events.
GiteaMirror commented 2026-05-01 06:14:45 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

@kspearrin the "back button event" happens with a Dell USB keyboard, too, it's not just my Yubikey that does it.

Thanks for being so responsive 👍

<!-- gh-comment-id:409342089 --> @bradfa commented on GitHub (Jul 31, 2018): @kspearrin the "back button event" happens with a Dell USB keyboard, too, it's not just my Yubikey that does it. Thanks for being so responsive :+1:
GiteaMirror commented 2026-05-01 06:14:48 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Its probably something to do with whatever event occurs whenever you plug in a USB device. I am not sure what that is

<!-- gh-comment-id:409342331 --> @kspearrin commented on GitHub (Jul 31, 2018): Its probably something to do with whatever event occurs whenever you plug in a USB device. I am not sure what that is
GiteaMirror commented 2026-05-01 06:14:52 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

@kspearrin the work around is to plug in the USB keyboard or Yubikey before starting to try and login to Bitwarden, then everything works fine with NFC on or off. So it's not urgent to fix this I don't think. Sorry I'm not that familiar with Xamarin (or even Java in general) so I'm not sure how much help I can be in debugging, sorry :(

<!-- gh-comment-id:409342875 --> @bradfa commented on GitHub (Jul 31, 2018): @kspearrin the work around is to plug in the USB keyboard or Yubikey before starting to try and login to Bitwarden, then everything works fine with NFC on or off. So it's not urgent to fix this I don't think. Sorry I'm not that familiar with Xamarin (or even Java in general) so I'm not sure how much help I can be in debugging, sorry :(
GiteaMirror commented 2026-05-01 06:14:54 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

On the home, click "Create Account". Then plug in the device. Does it take you back to home screen there too?

<!-- gh-comment-id:409343752 --> @kspearrin commented on GitHub (Jul 31, 2018): On the home, click "Create Account". Then plug in the device. Does it take you back to home screen there too?
GiteaMirror commented 2026-05-01 06:14:54 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Jul 31, 2018):

Yes. In "Create Account" if I plug in the Yubikey with NFC disabled it goes back to the home screen.

<!-- gh-comment-id:409344799 --> @bradfa commented on GitHub (Jul 31, 2018): Yes. In "Create Account" if I plug in the Yubikey with NFC disabled it goes back to the home screen.
GiteaMirror commented 2026-05-01 06:14:55 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 31, 2018):

Ok, that proves my theory then. Connecting a USB device is triggering the back event for some reason.

<!-- gh-comment-id:409349786 --> @kspearrin commented on GitHub (Jul 31, 2018): Ok, that proves my theory then. Connecting a USB device is triggering the back event for some reason.
GiteaMirror commented 2026-05-01 06:14:56 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 1, 2018):

Can you try updating to the beta to see if the same issue still occurs with the back button? https://play.google.com/apps/testing/com.x8bit.bitwarden

<!-- gh-comment-id:409426596 --> @kspearrin commented on GitHub (Aug 1, 2018): Can you try updating to the beta to see if the same issue still occurs with the back button? https://play.google.com/apps/testing/com.x8bit.bitwarden
GiteaMirror commented 2026-05-01 06:14:57 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Aug 1, 2018):

On 1.17.2 (1480) "beta" release from the Play store, I still get the crash when inserting Yubikey via USB when NFC is enabled. Crash at approximately 7:39am EDT.

<!-- gh-comment-id:409546874 --> @bradfa commented on GitHub (Aug 1, 2018): On 1.17.2 (1480) "beta" release from the Play store, I still get the crash when inserting Yubikey via USB when NFC is enabled. Crash at approximately 7:39am EDT.
GiteaMirror commented 2026-05-01 06:14:59 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Aug 1, 2018):

On 1.17.2 (1480) "beta" release from the Play store, the back button action still seems to occur when inserting Yubikey via USB when NFC is disabled.

<!-- gh-comment-id:409547253 --> @bradfa commented on GitHub (Aug 1, 2018): On 1.17.2 (1480) "beta" release from the Play store, the back button action still seems to occur when inserting Yubikey via USB when NFC is *disabled*.
GiteaMirror commented 2026-05-01 06:15:00 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 1, 2018):

I pushed build 1490 to the beta track on google play. This build prevents the back button action on the yubikey page. Can you give it a try and see if it works with 1490?

<!-- gh-comment-id:409728994 --> @kspearrin commented on GitHub (Aug 1, 2018): I pushed build 1490 to the beta track on google play. This build prevents the back button action on the yubikey page. Can you give it a try and see if it works with 1490?
GiteaMirror commented 2026-05-01 06:15:00 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Aug 2, 2018):

With build 1490, inserting my Yubikey via USB at the 2FA screen still results in the back operation happening with NFC off. Also, with NFC on and trying to use my Yubikey NEO via NFC for 2FA, after verifying the Yubikey the app crashes although the login seems to succeed as opening the app again requests only my master password to unlock my vault. Crash for this was at approximately 10:34am EDT today.

<!-- gh-comment-id:409949035 --> @bradfa commented on GitHub (Aug 2, 2018): With build 1490, inserting my Yubikey via USB at the 2FA screen still results in the back operation happening with NFC off. Also, with NFC on and trying to use my Yubikey NEO via NFC for 2FA, after verifying the Yubikey the app crashes although the login seems to succeed as opening the app again requests only my master password to unlock my vault. Crash for this was at approximately 10:34am EDT today.
GiteaMirror commented 2026-05-01 06:15:01 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 5, 2018):

Can you try again on 1491? Sorry, I don't have any other way to test this since my device doesn't have a USB port for a YubiKey

<!-- gh-comment-id:410489796 --> @kspearrin commented on GitHub (Aug 5, 2018): Can you try again on 1491? Sorry, I don't have any other way to test this since my device doesn't have a USB port for a YubiKey
GiteaMirror commented 2026-05-01 06:15:02 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Aug 7, 2018):

With 1491 the "back" action still seems to happen when inserting a Yubikey via USB at the 2FA screen when NFC is disabled.
With 1491 the crash still happens when inserting a Yubikey via USB at the 2FA screen when NFC is enabled. Crash at 11:51am EDT.

<!-- gh-comment-id:411106542 --> @bradfa commented on GitHub (Aug 7, 2018): With 1491 the "back" action still seems to happen when inserting a Yubikey via USB at the 2FA screen when NFC is disabled. With 1491 the crash still happens when inserting a Yubikey via USB at the 2FA screen when NFC is enabled. Crash at 11:51am EDT.
GiteaMirror commented 2026-05-01 06:15:02 -05:00
Author
Owner
Copy Link

@bradfa commented on GitHub (Aug 17, 2018):

Just to give a quick update, on build 1495 the crash still happens the same way. Crash at approximately 7:50 am EDT today if you need the logs.

<!-- gh-comment-id:413841883 --> @bradfa commented on GitHub (Aug 17, 2018): Just to give a quick update, on build 1495 the crash still happens the same way. Crash at approximately 7:50 am EDT today if you need the logs.
GiteaMirror commented 2026-05-01 06:15:02 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Aug 17, 2018):

Thanks. Unfortunately I don't have a good solution for this at this time.

<!-- gh-comment-id:413842602 --> @kspearrin commented on GitHub (Aug 17, 2018): Thanks. Unfortunately I don't have a good solution for this at this time.
GiteaMirror commented 2026-05-01 06:15:03 -05:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Feb 3, 2021):

Fixed by #1246

<!-- gh-comment-id:772188482 --> @eliykat commented on GitHub (Feb 3, 2021): Fixed by #1246
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#48711
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?