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

iOS app requires login when already set up #312

New Issue
Closed
opened 2025-11-07 08:34:59 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-07 08:34:59 -06:00
Owner
Copy Link

Originally created by @colinator19 on GitHub (Nov 29, 2018).

Every now and then (often enough to be a pain...) it appears that I have to login again on Bitwarden.
When I open the app, it does unlock with FaceID but it also states I can register or login while that was already done before.

Expected behaviour would be for the app to open the password library after validating via FaceID.

Once I press login; it did remember my email address but I have to put in the password again. It will work for a while but then suddely it wants me to login again even while FaceID still works (as it shows to do FaceID validation) but does not login again.

App Version: 1.20.0 (43)
iPhone X
iOS: 12.1
Self Hosted Bitwarden
Version: 2.5.0

Screens attached:
faceid_unlock

after_faceid_unlock

Originally created by @colinator19 on GitHub (Nov 29, 2018). Every now and then (often enough to be a pain...) it appears that I have to login again on Bitwarden. When I open the app, it does unlock with FaceID but it also states I can register or login while that was already done before. Expected behaviour would be for the app to open the password library after validating via FaceID. Once I press login; it did remember my email address but I have to put in the password again. It will work for a while but then suddely it wants me to login again even while FaceID still works (as it shows to do FaceID validation) but does not login again. App Version: 1.20.0 (43) iPhone X iOS: 12.1 Self Hosted Bitwarden Version: 2.5.0 Screens attached: ![faceid_unlock](https://user-images.githubusercontent.com/15741333/49256738-48b18080-f430-11e8-82fb-ea2503459b23.PNG) ![after_faceid_unlock](https://user-images.githubusercontent.com/15741333/49256740-4bac7100-f430-11e8-8314-9833c8449f95.PNG)
GiteaMirror commented 2025-11-07 08:35:00 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 30, 2018):

Weird. I have never seen this happen with TouchID. How often does this occur?

@kspearrin commented on GitHub (Nov 30, 2018): Weird. I have never seen this happen with TouchID. How often does this occur?
GiteaMirror commented 2025-11-07 08:35:00 -06:00
Author
Owner
Copy Link

@colinator19 commented on GitHub (Nov 30, 2018):

About 2/3 times a week but it is really random and depends on how often I use the app. I have not been able to put my finger on what scenarios this is being triggerd. It happened twice yesterday which is why I raised it now as an issue.

I believe the auto-fill function in iOS 12 is not being affected by this issue, it is always working. Looks like it is really upon opening the app intermittendly.

@colinator19 commented on GitHub (Nov 30, 2018): About 2/3 times a week but it is really random and depends on how often I use the app. I have not been able to put my finger on what scenarios this is being triggerd. It happened twice yesterday which is why I raised it now as an issue. I believe the auto-fill function in iOS 12 is not being affected by this issue, it is always working. Looks like it is really upon opening the app intermittendly.
GiteaMirror commented 2025-11-07 08:35:00 -06:00
Author
Owner
Copy Link

@colinator19 commented on GitHub (Dec 2, 2018):

It appears I have the same issue on my iPad Pro 2 which uses Touch ID. Just wanted to add it here.
I did however found something interesting - Without filling in my account details again, if I force close the app and reopen, it works and opens my safe correctly after Touch ID.

I also think I might know when this will occur, if you have used the app and then move to another app, after a while of inactivity, it will show this issue once you reopen it. I believe iOS does something to apps in the background that have not been used for a while to free up memory, I think this is the point where this issue might occur.

Just throwing in here what I know and see, hopefully to find the cause of this or atleast help for you to find the cause.

@colinator19 commented on GitHub (Dec 2, 2018): It appears I have the same issue on my iPad Pro 2 which uses Touch ID. Just wanted to add it here. I did however found something interesting - Without filling in my account details again, if I force close the app and reopen, it works and opens my safe correctly after Touch ID. I also think I might know when this will occur, if you have used the app and then move to another app, after a while of inactivity, it will show this issue once you reopen it. I believe iOS does something to apps in the background that have not been used for a while to free up memory, I think this is the point where this issue might occur. Just throwing in here what I know and see, hopefully to find the cause of this or atleast help for you to find the cause.
GiteaMirror commented 2025-11-07 08:35:01 -06:00
Author
Owner
Copy Link

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

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

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