Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Bitwarden Beta can't save Android App‘s password correctly #4082

Open
2 tasks done
chuwza opened this issue Oct 14, 2024 · 6 comments
Open
2 tasks done

[BUG] Bitwarden Beta can't save Android App‘s password correctly #4082

chuwza opened this issue Oct 14, 2024 · 6 comments
Labels

Comments

@chuwza
Copy link

chuwza commented Oct 14, 2024

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Go to an Android App
  2. Enter the App's account password
  3. Save the password by Bitwarden Beta
  4. Log out of the app and log back in
  5. The password you just saved is not displayed

Expected Result

Saved passwords can be associated with the app

Actual Result

As you can see in video, passwords saved by Bitwarden Beta can't be used by auto-fill, and I've found the reason why:

Bitwarden Beta is missing a string “androidapp://” when saving passwords, as shown in the picture, the right side of the picture associates the app with the password, which is OK (right app is KeyGuard, an alternative client for the Bitwarden) (https://github.com/AChep/keyguard-app), but the left side of the picture has the Bitwarden Beta does not associate the app with the password when saving the password. I can't see the “androidapp://” string even when I click the settings icon for that URI.

So passwords saved through Bitwarden Beta are not actually available, only in browsers, but not for Android Apps.

Screenshots or Videos

VIDEO IS HERE

screen-20241012-204947.-.Compressed.with.FlexClip.mp4

PIcture
IMG_20241012_204326

Additional Context

I use the official Bitwarden Beta, official server

Build Version

© Bitwarden Inc. 2015-2024 Version: 2024.9.0 (19209)

Environment Details

Any device
Any OS

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.
@chuwza chuwza added the bug label Oct 14, 2024
@bitwarden-bot
Copy link

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

@daniellbw
Copy link

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!

@maxmini1
Copy link

@chuwza Hi there sounds like its fixed tyr the new release 2024.11.3 (19432)

@chuwza
Copy link
Author

chuwza commented Nov 12, 2024

@chuwza Hi there sounds like its fixed tyr the new release 2024.11.3 (19432)

Sorry, I test the 2024.11.3 (19432), The bug has not been fixed🥲
Screenshot_20241112-185444_Bitwarden_Beta~2

@Gammachange
Copy link

Gammachange commented Nov 12, 2024

@chuwza I confirm its new work on the new release
2024.11.3 (19432)
Sounds like its just for you!
See here -
https://github.com/user-attachments/assets/d8bf67d3-0845-4b19-b27e-3caaed5e7e34

and here -

ScreenRecording_20241112_111947.mp4

@chuwza
Copy link
Author

chuwza commented Nov 12, 2024

@chuwza I confirm its new work on the new release 2024.11.3 (19432) Sounds like its just for you! See here - https://github.com/user-attachments/assets/d8bf67d3-0845-4b19-b27e-3caaed5e7e34

and here -

ScreenRecording_20241112_111947.mp4

Yes, I repeated your steps and in this case the bug was indeed fixed.

screen-20241112-194208.mp4

However, in the case of ‘After entering the password for the app, Bitwarden pops up an autosave prompt and selects save’, the bug is still not fixed.

screen-20241112-194249.mp4

In other words, the bug is half fixed😂😥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants