Inconsistency: Card numbers are not shown in groups (while in the other BW apps they are in groups of four) #2221

Open
opened 2025-11-26 23:12:13 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @pamperer562580892423 on GitHub (May 6, 2025).

Steps To Reproduce

  1. Go to an existing Card item with a Card number - or create a new Card item with a Card number.
  2. Open the "View item" view for that Card.
  3. Toggle visibility of the Card number.

Expected Result

Card numbers are grouped - like in the browser extension, in the desktop app and in the web vault.

Actual Result

Card numbers are not grouped. An inconsistency, as they are grouped in the other BW apps.

Screenshots or Videos

Android mobile app (2025.4.0) - the numbers are NOT grouped:

Image

 

Browser extension (2025.4.0) - the numbers ARE grouped:

Image

 

(Windows) Desktop app (2025.3.0) - the numbers ARE grouped:

Image

 

Web vault (2025.4.1) - the numbers ARE grouped:

Image

Additional Context

I just used eight "groups" of four numbers for visualization. - Of course, that is longer as a normal card number. I found it interesting though, that the "grouping" stops also in the other three BW apps after the fourth group. I'm not sure, if there are (or ever will be) longer card numbers than now, so I'm not sure if the grouping for more than four groups of four numbers should also be adapted in all BW apps?!?

Build Version

2025.4.0

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Fairphone 5
  • 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 @pamperer562580892423 on GitHub (May 6, 2025). ### Steps To Reproduce 1. Go to an existing Card item with a Card number - or create a new Card item with a Card number. 2. Open the "View item" view for that Card. 3. Toggle visibility of the Card number. ### Expected Result Card numbers are grouped - like in the browser extension, in the desktop app and in the web vault. ### Actual Result Card numbers are not grouped. An inconsistency, as they **are** grouped in the other BW apps. ### Screenshots or Videos **Android mobile app** (2025.4.0) - the numbers are NOT grouped: ![Image](https://github.com/user-attachments/assets/210a575a-3739-4b0a-86d2-775b9c7140ff)   **Browser extension** (2025.4.0) - the numbers ARE grouped: ![Image](https://github.com/user-attachments/assets/08f93006-db40-48dd-8a19-90773939a4b1)   (Windows) **Desktop app** (2025.3.0) - the numbers ARE grouped: ![Image](https://github.com/user-attachments/assets/d7d5e405-ef6c-413b-a76f-9375f4af7157)   **Web vault** (2025.4.1) - the numbers ARE grouped: ![Image](https://github.com/user-attachments/assets/b9d90067-366a-47c0-807d-e9620cf4f37a) ### Additional Context I just used eight "groups" of four numbers for visualization. - Of course, that is longer as a normal card number. I found it interesting though, that the "grouping" stops also in the other three BW apps after the fourth group. I'm not sure, if there are (or ever will be) longer card numbers than now, so I'm not sure if the grouping for more than four groups of four numbers should also be adapted in all BW apps?!? ### Build Version 2025.4.0 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details - Fairphone 5 - 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:password-managerbug labels 2025-11-26 23:12:13 -06:00
Author
Owner

@S-Kakar commented on GitHub (May 6, 2025):

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

@S-Kakar commented on GitHub (May 6, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-21264
Author
Owner

@rmcdowell-bitwarden commented on GitHub (May 12, 2025):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

@rmcdowell-bitwarden commented on GitHub (May 12, 2025): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
Author
Owner

@pamperer562580892423 commented on GitHub (May 15, 2025):

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Only, that the same issue seems to also be the case for the iOS mobile app - see this post: https://community.bitwarden.com/t/credit-number-not-in-groups-of-4-digits/84823/8

@pamperer562580892423 commented on GitHub (May 15, 2025): > If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Only, that the same issue seems to also be the case for the iOS mobile app - see this post: https://community.bitwarden.com/t/credit-number-not-in-groups-of-4-digits/84823/8
Author
Owner

@rmcdowell-bitwarden commented on GitHub (May 16, 2025):

@pamperer562580892423 thank you for mentioning that! I've included the iOS behavior in our internal board for our engineering team to review.

@rmcdowell-bitwarden commented on GitHub (May 16, 2025): @pamperer562580892423 thank you for mentioning that! I've included the iOS behavior in our internal board for our engineering team to review.
Author
Owner

@EDIflyer commented on GitHub (Jun 8, 2025):

Thanks for raising @pamperer562580892423 - confirm identical issue on Android 15 here, has been like this for as long as I can remember - would be great to get this fixed.

@EDIflyer commented on GitHub (Jun 8, 2025): Thanks for raising @pamperer562580892423 - confirm identical issue on Android 15 here, has been like this for as long as I can remember - would be great to get this fixed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2221