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

[GH-ISSUE #3387] F-Droid Version: Account security login requests causes nonexistent notification flow #27813

New Issue
Closed
opened 2026-04-18 11:24:24 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-18 11:24:24 -05:00
Owner
Copy Link

Originally created by @onkoe on GitHub (Jun 30, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3387

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. Open up Bitwarden Kotlin with the F-Droid build
  2. Head to app Settings > Account security.
  3. Toggle on "Use this device to approve login requests from other devices"
  4. Select "Yes" on the message box.
  5. A new message box will appear, stating that you can "Receive push notifications for new login requests", with "No thanks" and "Settings" buttons.
  6. Select Settings, then hit "Notifications"
  7. The switch will be grayed out due to there being no Firebase support in the F-Droid build.

Expected Result

On F-Droid builds, do not enable any settings that require notifications.

Actual Result

Asks the user to enable a statically turned off notifications switch.

Screenshots or Videos

Screenshot_20240630-174000_Settings

Additional Context

No response

Build Version

© Bitwarden Inc. 2015-2024 Version: 2024.6.0 (10746)

Environment Details

  • Device: OnePlus 7 Pro
  • Environment
    • Distribution: LineageOS for microG 21
    • OS: Android 14

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 @onkoe on GitHub (Jun 30, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3387 ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Open up Bitwarden Kotlin with the F-Droid build 2. Head to app Settings > Account security. 3. Toggle on "Use this device to approve login requests from other devices" 4. Select "Yes" on the message box. 5. A new message box will appear, stating that you can "Receive push notifications for new login requests", with "No thanks" and "Settings" buttons. 6. Select Settings, then hit "Notifications" 7. The switch will be grayed out due to there being no Firebase support in the F-Droid build. ### Expected Result On F-Droid builds, do not enable any settings that require notifications. ### Actual Result Asks the user to enable a statically turned off notifications switch. ### Screenshots or Videos ![Screenshot_20240630-174000_Settings](https://github.com/bitwarden/android/assets/66580279/75b3d8b7-c8ad-4071-9975-fd7e0c7b8fa1) ### Additional Context _No response_ ### Build Version © Bitwarden Inc. 2015-2024 Version: 2024.6.0 (10746) ### Environment Details - Device: OnePlus 7 Pro - Environment - Distribution: LineageOS for microG 21 - OS: Android 14 ### 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 bug label 2026-04-18 11:24:24 -05:00
GiteaMirror commented 2026-04-18 11:24:25 -05:00
Author
Owner
Copy Link

@sammbw commented on GitHub (Jul 1, 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!

<!-- gh-comment-id:2199191046 --> @sammbw commented on GitHub (Jul 1, 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!
GiteaMirror commented 2026-04-18 11:24:26 -05:00
Author
Owner
Copy Link

@zzjjaayy commented on GitHub (Jul 2, 2024):

@sammbw {sorry for tagging if this is not how you do it}, I wanted to know if this and other issues on github are up for grabs by independent contributors?

<!-- gh-comment-id:2202745846 --> @zzjjaayy commented on GitHub (Jul 2, 2024): @sammbw {sorry for tagging if this is not how you do it}, I wanted to know if this and other issues on github are up for grabs by independent contributors?
GiteaMirror commented 2026-04-18 11:24:27 -05:00
Author
Owner
Copy Link

@micahblut commented on GitHub (Jul 11, 2024):

@onkoe the version you listed is not a native app build. Please be aware that legacy .NET app bugs should be reported in [bitwarden/mobile]

<!-- gh-comment-id:2222690670 --> @micahblut commented on GitHub (Jul 11, 2024): @onkoe the version you listed is not a native app build. Please be aware that legacy .NET app bugs should be reported in [[bitwarden/mobile](https://github.com/bitwarden/mobile)]
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#27813
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?