[GH-ISSUE #4829] Authenticator return "Key is invalid." when typing key provided by Samsung account #50018

Closed
opened 2026-05-01 11:06:02 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @th1nhhdk on GitHub (Jul 6, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4829

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.
Originally created by @th1nhhdk on GitHub (Jul 6, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4829 ### 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 - [X] 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.
GiteaMirror added the app:authenticatorbug labels 2026-05-01 11:06:03 -05:00
Author
Owner

@HeyITGuyFixIt commented on GitHub (Sep 9, 2024):

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.

<!-- gh-comment-id:2704949120 --> @HeyITGuyFixIt commented on GitHub (Sep 9, 2024): 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.
Author
Owner

@tixsys commented on GitHub (Sep 27, 2024):

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

<!-- gh-comment-id:2704949127 --> @tixsys commented on GitHub (Sep 27, 2024): Went here to report same. To solve u need to remove spaces. And bitwarsen should do it automatically
Author
Owner

@HeyITGuyFixIt commented on GitHub (Sep 28, 2024):

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

<!-- gh-comment-id:2704949130 --> @HeyITGuyFixIt commented on GitHub (Sep 28, 2024): @tixsys at least with notesnook, it still says invalid key after removing the spaces.
Author
Owner

@Cryptnym commented on GitHub (Sep 28, 2024):

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

<!-- gh-comment-id:2704949136 --> @Cryptnym commented on GitHub (Sep 28, 2024): Im getting the same issue trying to add a gmail account, i tried removing the spaces but still get "key is invalid"
Author
Owner

@SaintPatrck commented on GitHub (Oct 2, 2024):

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.

<!-- gh-comment-id:2704949145 --> @SaintPatrck commented on GitHub (Oct 2, 2024): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#50018