github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 21:10:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

Don't say no items in vault initially before verifying #1766

New Issue
Closed
opened 2025-11-26 22:57:35 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-26 22:57:35 -06:00
Owner
Copy Link

Originally created by @jidanni on GitHub (Nov 19, 2023).

Steps To Reproduce

With the Android app, on a highly loaded, slow network, login to your vault, with the master password.

Expected Result

We see we have 543 items in our vault.

Actual Result

However, before we see that, for a very short split second, we see "no items in your vault."

Screenshots or Videos

Hard to make a screenshot because it happens so fast.

Additional Context

So there's just simply being the mistake of first using always using that splash screen saying no items in vault, while in the background there's some checking going on.

The thought probably being that an empty response is the same as zero, so we don't have to replace the splash screen during that time.

However, it does panic users a very large amount even if for a very short time.

So you simply need to have an additional splash screen: "connecting...".

And only after you're sure of what the answer is from the server, only then should you show the statement of the results. Otherwise it is an absolute bug to show the wrong information, even if for not very long.

I must reiterate with your fancy laboratory situation you're not going to reproduce this bug. You need a highly loaded network and cell phone.

Or maybe that screen I saw is just part of the initial screen even before connection is attempted and never intended for the user to see it very long: but I saw it anyway.

Please don't expect me to do videos and screenshots of it because I'm not set up for it.

Operating System

Android

Operating System Version

No response

Device

Asus Zenfone 3

Build Version

Latest

Beta

  • Using a pre-release version of the application.
Originally created by @jidanni on GitHub (Nov 19, 2023). ### Steps To Reproduce With the Android app, on a highly loaded, slow network, login to your vault, with the master password. ### Expected Result We see we have 543 items in our vault. ### Actual Result However, before we see that, for a very short split second, we see "no items in your vault." ### Screenshots or Videos Hard to make a screenshot because it happens so fast. ### Additional Context So there's just simply being the mistake of first using always using that splash screen saying no items in vault, while in the background there's some checking going on. The thought probably being that an empty response is the same as zero, so we don't have to replace the splash screen during that time. However, it does panic users a very large amount even if for a very short time. So you simply need to have an additional splash screen: "connecting...". And only after you're sure of what the answer is from the server, only then should you show the statement of the results. Otherwise it is an absolute bug to show the wrong information, even if for not very long. I must reiterate with your fancy laboratory situation you're not going to reproduce this bug. You need a highly loaded network and cell phone. Or maybe that screen I saw is just part of the initial screen even before connection is attempted and never intended for the user to see it very long: but I saw it anyway. Please don't expect me to do videos and screenshots of it because I'm not set up for it. ### Operating System Android ### Operating System Version _No response_ ### Device Asus Zenfone 3 ### Build Version Latest ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:57:35 -06:00
GiteaMirror commented 2025-11-26 22:57:36 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Nov 20, 2023):

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!

@Krychaz commented on GitHub (Nov 20, 2023): 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!
GiteaMirror commented 2025-11-26 22:57:36 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/2874

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/2874
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 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#1766
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?