Originally created by @aksdb on GitHub (Dec 16, 2018).
In the current version of bitwarden_rs, I can no longer login with the Bitwarden Android client with accounts that have 2FA enabled. The app immediately closes.
Since my Android development setup is still kinda sucky (or I suck at using it :-)) the only thing I got out of the debugger was "System.InvalidOperationException: Token not found." without a proper stacktrace.
I presume something in the response is missing. Or maybe simply the casing of the key(s) is different? Apparently it works in the jslib implementation, so it has to be something that the C# implementation of the mobile apps does differently.
Originally created by @aksdb on GitHub (Dec 16, 2018).
In the current version of bitwarden_rs, I can no longer login with the Bitwarden Android client with accounts that have 2FA enabled. The app immediately closes.
Since my Android development setup is still kinda sucky (or I suck at using it :-)) the only thing I got out of the debugger was "System.InvalidOperationException: Token not found." without a proper stacktrace.
I presume something in the response is missing. Or maybe simply the casing of the key(s) is different? Apparently it works in the jslib implementation, so it has to be something that the C# implementation of the mobile apps does differently.
I've run into this as well. The log for bitwarden_rs claims the login attempt succeeded, but the Android app really didn't like whatever response bitwarden_rs gave.
@tycho commented on GitHub (Dec 16, 2018):
I've run into this as well. The log for bitwarden_rs claims the login attempt succeeded, but the Android app really didn't like whatever response bitwarden_rs gave.
You were right, it was because of a casing issue. That was solved some time ago for the JSON API. But the login is a normal form instead. It should be fixed now in the latest master, tested on iOS.
@dani-garcia commented on GitHub (Dec 16, 2018):
You were right, it was because of a casing issue. That was solved some time ago for the JSON API. But the login is a normal form instead. It should be fixed now in the latest master, tested on iOS.
@mprasil commented on GitHub (Dec 16, 2018):
Image from master [is now building](https://cloud.docker.com/repository/registry-1.docker.io/mprasil/bitwarden/builds/3f994979-c6e9-4cac-9195-14a15ec813d2). Give it about an hour.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @aksdb on GitHub (Dec 16, 2018).
In the current version of bitwarden_rs, I can no longer login with the Bitwarden Android client with accounts that have 2FA enabled. The app immediately closes.
Since my Android development setup is still kinda sucky (or I suck at using it :-)) the only thing I got out of the debugger was "System.InvalidOperationException: Token not found." without a proper stacktrace.
I presume something in the response is missing. Or maybe simply the casing of the key(s) is different? Apparently it works in the jslib implementation, so it has to be something that the C# implementation of the mobile apps does differently.
@tycho commented on GitHub (Dec 16, 2018):
I've run into this as well. The log for bitwarden_rs claims the login attempt succeeded, but the Android app really didn't like whatever response bitwarden_rs gave.
@dani-garcia commented on GitHub (Dec 16, 2018):
You were right, it was because of a casing issue. That was solved some time ago for the JSON API. But the login is a normal form instead. It should be fixed now in the latest master, tested on iOS.
@mprasil commented on GitHub (Dec 16, 2018):
Image from master is now building. Give it about an hour.
@tycho commented on GitHub (Dec 17, 2018):
@dani-garcia Confirmed, that fixed it!
@aksdb commented on GitHub (Dec 17, 2018):
Thanks @dani-garcia (and @mprasil) for getting a fix out that fast. Works fine now :-)