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

[GH-ISSUE #5486] Unable to add TOTP secret key longer than 18 characters #39239

New Issue
Open
opened 2026-04-23 17:58:18 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-23 17:58:18 -05:00
Owner
Copy Link

Originally created by @rmcdowell-bitwarden on GitHub (Jul 7, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5486

Steps To Reproduce

  1. Open the Authenticator app
  2. Tap the + icon to add a new entry
  3. Tap "Enter key manually"
  4. Enter a key longer than 18 characters

Expected Result

A TOTP entry will be created

Actual Result

Receive the error message "Key is invalid"

Screenshots or Videos

No response

Additional Context

A TOTP secret key longer than 18 characters works on the iOS Bitwarden Authenticator app and when using Bitwarden's Integrated Authenticator

Build Version

2025.6.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

-Device: Samsung Galaxy S25+

  • Android 15
  • One UI 7.0

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 @rmcdowell-bitwarden on GitHub (Jul 7, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5486 ### Steps To Reproduce 1. Open the Authenticator app 2. Tap the + icon to add a new entry 3. Tap "Enter key manually" 4. Enter a key longer than 18 characters ### Expected Result A TOTP entry will be created ### Actual Result Receive the error message "Key is invalid" ### Screenshots or Videos _No response_ ### Additional Context A TOTP secret key longer than 18 characters works on the iOS Bitwarden Authenticator app and when using Bitwarden's Integrated Authenticator ### Build Version 2025.6.0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details -Device: Samsung Galaxy S25+ - Android 15 - One UI 7.0 ### 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-04-23 17:58:18 -05:00
GiteaMirror commented 2026-04-23 17:58:20 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jul 7, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-23470

<!-- gh-comment-id:3043881071 --> @bitwarden-bot commented on GitHub (Jul 7, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-23470
GiteaMirror commented 2026-04-23 17:58:21 -05:00
Author
Owner
Copy Link

@Amirnlz commented on GitHub (Jul 16, 2025):

I’ve tested the flow with a TOTP secret key longer than 18 characters (specifically 32 characters), and everything worked as expected — I didn’t encounter any errors.

Here is the test result:

Image

It might be helpful to know a bit more about the steps you're following. For example:

  • Are you entering the key manually or using a QR code?
  • Is the key being rejected immediately, or is the problem occurring later (e.g., during code generation)?
  • Are there any specific error messages or console logs?

With more context, I'd be happy to help investigate further or assist with a fix. Thanks!

<!-- gh-comment-id:3077622551 --> @Amirnlz commented on GitHub (Jul 16, 2025): I’ve tested the flow with a TOTP secret key longer than 18 characters (specifically 32 characters), and everything worked as expected — I didn’t encounter any errors. Here is the test result: <img width="411" height="126" alt="Image" src="https://github.com/user-attachments/assets/50f93289-ff58-44ff-b486-788a520a8c7f" /> It might be helpful to know a bit more about the steps you're following. For example: * Are you entering the key manually or using a QR code? * Is the key being rejected immediately, or is the problem occurring later (e.g., during code generation)? * Are there any specific error messages or console logs? With more context, I'd be happy to help investigate further or assist with a fix. Thanks!
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 app:authenticator bug
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#39239
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?