Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Authenticator return "Key is invalid." when typing key provided by Samsung account #141

Open
1 task done
th1nhhdk opened this issue Jul 6, 2024 · 5 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@th1nhhdk
Copy link

th1nhhdk commented Jul 6, 2024

Steps To Reproduce

  1. Go to 'Add item'
  2. Click on 'Enter key manually.'
  3. Type key (key format is "abcd abcd abcd abcd")
  4. Click on 'Add code'

Expected Result

Works like in "Microsoft Authenticator"

Actual Result

It returns "Key is invalid."

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.6.2 (340)

Environment Details

  • Device: Sony Xperia 1 II
  • OS Version: LineageOS 21 (Android 14)

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@th1nhhdk th1nhhdk added the bug Something isn't working label Jul 6, 2024
@HeyITGuyFixIt
Copy link

I just encountered this exact issue when attempting to add a key (copy and paste) from Notesnook. My device is a Google Pixel 6a running stock Android 14.

@tixsys
Copy link

tixsys commented Sep 27, 2024

Went here to report same. To solve u need to remove spaces. And bitwarsen should do it automatically

@HeyITGuyFixIt
Copy link

@tixsys at least with notesnook, it still says invalid key after removing the spaces.

@Cryptnym
Copy link

Im getting the same issue trying to add a gmail account, i tried removing the spaces but still get "key is invalid"

@SaintPatrck
Copy link
Contributor

Hi all,

Thank you for reporting your issue. We use strict Base32 validation when manually entering keys. Spaces, lower-case letters, and other non-base32 characters will cause validation to fail. When displaying keys for manual entry, many applications may use lower-case letters or include spaces. I suggest double checking the code you entered contains only valid Base32 characters.

FYI; validation rules were relaxed to ignore spaces in a recent commit, but lower-case letters are still considered invalid. That change will be published soon.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants