github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-21 22:00:42 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Missing login on mobile [Android] #53

New Issue
Closed
opened 2025-11-07 08:24:45 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-07 08:24:45 -06:00
Owner
Copy Link

Originally created by @renolc on GitHub (May 7, 2017).

I have a Nexus 5X on Android 7.1.2 with the current latest version of bitwarden -- 1.5.0 (553).

I'm not entirely sure when this started happening, but I just noticed today that I have a login that just isn't showing up on my phone at all. It's still present in the Chrome extension as well as the web vault, so I know it's there.

This could potentially be related to the new sharing feature. I set up an Org where I am the only current member and I started sharing certain logins to it. The login in question was not shared, but it was the only one in that folder that wasn't. All other logins seem to be appearing correctly, it's just this one login that isn't.

I tried force syncing a few times in different orders. I even tried deleting and recreating the login to no avail.

Originally created by @renolc on GitHub (May 7, 2017). I have a Nexus 5X on Android 7.1.2 with the current latest version of bitwarden -- 1.5.0 (553). I'm not entirely sure when this started happening, but I just noticed today that I have a login that just isn't showing up on my phone at all. It's still present in the Chrome extension as well as the web vault, so I know it's there. This could potentially be related to the new sharing feature. I set up an Org where I am the only current member and I started sharing certain logins to it. The login in question was not shared, but it was the only one in that folder that wasn't. All other logins seem to be appearing correctly, it's just this one login that isn't. I tried force syncing a few times in different orders. I even tried deleting and recreating the login to no avail.
GiteaMirror commented 2025-11-07 08:24:46 -06:00
Author
Owner
Copy Link

@renolc commented on GitHub (May 7, 2017):

Doing some further testing, it seems my Android bitwarden isn't picking up any new logins at all. I just tried creating a new dummy one for github, force syncing the chrome extension, then force syncing the android app, and the new github didn't show up.

@renolc commented on GitHub (May 7, 2017): Doing some further testing, it seems my Android bitwarden isn't picking up any new logins at all. I just tried creating a new dummy one for github, force syncing the chrome extension, then force syncing the android app, and the new github didn't show up.
GiteaMirror commented 2025-11-07 08:24:46 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 7, 2017):

Can you try logging out and back in to see if that changes anything?

@kspearrin commented on GitHub (May 7, 2017): Can you try logging out and back in to see if that changes anything?
GiteaMirror commented 2025-11-07 08:24:46 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 7, 2017):

Also this new one you just tested for github, is it still just on android that it isn't showing up?

@kspearrin commented on GitHub (May 7, 2017): Also this new one you just tested for github, is it still just on android that it isn't showing up?
GiteaMirror commented 2025-11-07 08:24:46 -06:00
Author
Owner
Copy Link

@renolc commented on GitHub (May 7, 2017):

Yes, I forgot to mention I tried logging in and out. Correct, only on Android is it not showing up.

Also, I just tried to create a new login directly on the phone and during save it seemed to crash. Didn't get a notification of a crash, but it completely closed and on reopen it didn't have the new login. I might try uninstall and reinstall to see if that helps.

@renolc commented on GitHub (May 7, 2017): Yes, I forgot to mention I tried logging in and out. Correct, only on Android is it not showing up. Also, I just tried to create a new login directly on the phone and during save it seemed to crash. Didn't get a notification of a crash, but it completely closed and on reopen it didn't have the new login. I might try uninstall and reinstall to see if that helps.
GiteaMirror commented 2025-11-07 08:24:47 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 7, 2017):

When you force sync does the toast notification say that is was successful or failed?

@kspearrin commented on GitHub (May 7, 2017): When you force sync does the toast notification say that is was successful or failed?
GiteaMirror commented 2025-11-07 08:24:47 -06:00
Author
Owner
Copy Link

@renolc commented on GitHub (May 7, 2017):

It says "syncing complete" and updates the timestamp. It doesn't specify success or failure, but it seems like a success due to the lack of a failure notice and the updated timestamp.

@renolc commented on GitHub (May 7, 2017): It says "syncing complete" and updates the timestamp. It doesn't specify success or failure, but it seems like a success due to the lack of a failure notice and the updated timestamp.
GiteaMirror commented 2025-11-07 08:24:47 -06:00
Author
Owner
Copy Link

@renolc commented on GitHub (May 7, 2017):

Reinstalling seems to have fixed it. All previously missing logins are now present, including the ones I just previously created on the phone itself. Creating new entries on the phone also works as expected again. I'll go ahead and close this issue since it seems to have been environmental.

Thanks!

@renolc commented on GitHub (May 7, 2017): Reinstalling seems to have fixed it. All previously missing logins are now present, including the ones I just previously created on the phone itself. Creating new entries on the phone also works as expected again. I'll go ahead and close this issue since it seems to have been environmental. Thanks!
GiteaMirror commented 2025-11-07 08:24:47 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 7, 2017):

Very weird. I wish I could have figured out what was going on since it is likely that there is actually some underlying bug. Regardless, glad you're working now.

@kspearrin commented on GitHub (May 7, 2017): Very weird. I wish I could have figured out what was going on since it is likely that there is actually some underlying bug. Regardless, glad you're working now.
GiteaMirror commented 2025-11-07 08:24:48 -06:00
Author
Owner
Copy Link

@CircuitGuy commented on GitHub (Apr 18, 2018):

So... Do you still want a test case? Got this issue 2x now. Won't sync to the shared vault and (I think - maybe human error) BitWarden is "forgetting" some new entries created in the app. Happened once before and I cleared all data to fix the issue.

@CircuitGuy commented on GitHub (Apr 18, 2018): So... Do you still want a test case? Got this issue 2x now. Won't sync to the shared vault and (I think - maybe human error) BitWarden is "forgetting" some new entries created in the app. Happened once before and I cleared all data to fix the issue.
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
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#53
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?