Folder Number doesn't match between Android application and Web Extension #1922

Closed
opened 2025-11-26 23:01:48 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @s4ln1x on GitHub (Jun 26, 2024).

Steps to reproduce the issue

  1. Go to your web extension and check the number of folders there and write that number
  2. Got to your android mobile application and check the number of folders there and write that number
  3. Verify if the folder number is the same

Steps in Action

  1. 16 folders on chrome on MacOS
    Screenshot 2024-06-26 at 9 20 15

  2. 17 folders on Bitwareden Android application
    Screenshot_20240626_092345

  3. The folder number detected by each application differs, in this case the web extension is correct as I have 16 folders whereas the Android application is counting the "No Folder" as a folder

Expected Result

The folder number value should be the same

Actual Result

The folder number value differs from the Android application and the web extension

Screenshots or Videos

Android
Screenshot_20240626_092345

Web Extension
Screenshot 2024-06-26 at 9 20 15

Additional Context

No response

Build Version

Android (2024.6.0) Web Extension (2024.4.2)

Environment Details

Android

  • Samsung Galaxy S21 Ultra
  • Android 14
  • One UI version 6.1

Web Extension

  • Chrome Browser (Version 126.0.6478.116 (Official Build) (arm64))
  • MacOS Sonoma 14.5
  • MacBook Pro M1

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 @s4ln1x on GitHub (Jun 26, 2024). ## Steps to reproduce the issue 1. Go to your web extension and check the number of folders there and write that number 2. Got to your android mobile application and check the number of folders there and write that number 3. Verify if the folder number is the same ## Steps in Action 1. 16 folders on chrome on MacOS <img width="376" alt="Screenshot 2024-06-26 at 9 20 15" src="https://github.com/bitwarden/android/assets/44090859/2fe9bec5-855a-4f44-8a8d-2972658b3300"> 2. 17 folders on Bitwareden Android application ![Screenshot_20240626_092345](https://github.com/bitwarden/android/assets/44090859/2a48dbe8-1503-427f-bb24-069e684b2d82) 3. The folder number detected by each application differs, in this case the web extension is correct as I have 16 folders whereas the Android application is counting the "No Folder" as a folder ### Expected Result The folder number value should be the same ### Actual Result The folder number value differs from the Android application and the web extension ### Screenshots or Videos Android ![Screenshot_20240626_092345](https://github.com/bitwarden/android/assets/44090859/80314685-068e-4453-a573-8d2da0044907) Web Extension <img width="376" alt="Screenshot 2024-06-26 at 9 20 15" src="https://github.com/bitwarden/android/assets/44090859/10dbea16-1e12-424f-903c-7c9580fd87c8"> ### Additional Context _No response_ ### Build Version Android (2024.6.0) Web Extension (2024.4.2) ### Environment Details ## Android - Samsung Galaxy S21 Ultra - Android 14 - One UI version 6.1 ## Web Extension - Chrome Browser (Version 126.0.6478.116 (Official Build) (arm64)) - MacOS Sonoma 14.5 - MacBook Pro M1 ### 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:01:48 -06:00
Author
Owner

@cbbit commented on GitHub (Jun 26, 2024):

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!

@cbbit commented on GitHub (Jun 26, 2024): 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

@closebot-bw commented on GitHub (Aug 12, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (August 26, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

@closebot-bw commented on GitHub (Aug 12, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (August 26, 2025) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
Author
Owner

@closebot-bw commented on GitHub (Aug 23, 2025):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 3 days (August 26, 2025) if no further activity occurs.

If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure.

We appreciate your understanding and contribution to keeping our issue tracker organized! 📋

@closebot-bw commented on GitHub (Aug 23, 2025): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **3 days** (August 26, 2025) if no further activity occurs. If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure. We appreciate your understanding and contribution to keeping our issue tracker organized! 📋
Author
Owner

@closebot-bw commented on GitHub (Aug 26, 2025):

🔒 Issue Closed Due to Inactivity

This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.

If this issue is still relevant:

  • Please create a new issue with updated information
  • Include steps to reproduce the problem if it's a bug report
  • Mention if this issue still occurs in the latest version

Thank you for your contribution to this project. Your feedback helps us improve! 🙏

@closebot-bw commented on GitHub (Aug 26, 2025): 🔒 **Issue Closed Due to Inactivity** This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities. **If this issue is still relevant:** - Please create a new issue with updated information - Include steps to reproduce the problem if it's a bug report - Mention if this issue still occurs in the latest version Thank you for your contribution to this project. Your feedback helps us improve! 🙏
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1922