github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-07-16 23:25:17 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #4319] Push Notifications Broken #95302

New Issue
Closed
opened 2026-05-30 15:17:49 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-30 15:17:49 -05:00
Owner
Copy Link

Originally created by @larena1 on GitHub (Nov 16, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4319

Steps To Reproduce

Request device login

Expected Result

Push notification

Actual Result

No notification

FCM shows the message and broadcasts it but Bitwarden does not seem to be handling it. Renamed vault items will also only change when syncing manually.

Screenshots or Videos

No response

Additional Context

No response

Build Version

Version 2024.11.6 com.x8bit.bitwarden

What server are you connecting to?

Self-host

Self-host Server Version

No response

Environment Details

No response

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 @larena1 on GitHub (Nov 16, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4319 ### Steps To Reproduce Request device login ### Expected Result Push notification ### Actual Result No notification FCM shows the message and broadcasts it but Bitwarden does not seem to be handling it. Renamed vault items will also only change when syncing manually. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version Version 2024.11.6 com.x8bit.bitwarden ### What server are you connecting to? Self-host ### Self-host Server Version _No response_ ### Environment Details _No response_ ### 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.
GiteaMirror added the bug label 2026-05-30 15:17:49 -05:00
GiteaMirror commented 2026-05-30 15:17:53 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Nov 16, 2024):

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

<!-- gh-comment-id:2480855201 --> @bitwarden-bot commented on GitHub (Nov 16, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-14974
GiteaMirror commented 2026-05-30 15:17:56 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Nov 19, 2024):

Hello @larena1,

Thank you for reporting this. In testing, I am being presented with a Login request notification; This makes me suspect that this is stemming from how the self-hosted server in question is set up or the environment (proxy/firewall/etc.) it's in. With that in mind, I highly recommend that you review the network configuration and check what could be interfering with the communication between the Bitwarden server and the Bitwarden client(s).

If this behaviour persists, please feel free to create a Support ticket so we'd have a look at this together, and please also include a link to this GitHub report in the body of your ticket; Also, please state the version of your Bitwarden server, clarify if you're using vaultwarden (bitwarden_rs), and mention the operating system of the approving device/client.

Alternatively, you can seek assistance from other Bitwarden users in our Community Forums, if you wish.

We use GitHub to track potential bugs and other development related matters; This GitHub report will be closed at this point.

Thank you again,

<!-- gh-comment-id:2485646892 --> @SergeantConfused commented on GitHub (Nov 19, 2024): Hello @larena1, Thank you for reporting this. In testing, I am being presented with a Login request notification; This makes me suspect that this is stemming from how the self-hosted server in question is set up or the environment (proxy/firewall/etc.) it's in. With that in mind, I highly recommend that you review the network configuration and check what could be interfering with the communication between the Bitwarden server and the Bitwarden client(s). If this behaviour persists, please feel free to create a [Support ticket](https://bitwarden.com/help/) so we'd have a look at this together, and please also include a link to this GitHub report in the body of your ticket; Also, please state the version of your Bitwarden server, clarify if you're using vaultwarden (bitwarden_rs), and mention the operating system of the approving device/client. Alternatively, you can seek assistance from other Bitwarden users in our [Community Forums](https://community.bitwarden.com/c/support/), if you wish. We use GitHub to track potential bugs and other development related matters; This GitHub report will be closed at this point. Thank you again,
GiteaMirror commented 2026-05-30 15:17:57 -05:00
Author
Owner
Copy Link

@larena1 commented on GitHub (Nov 19, 2024):

@SergeantConfused is there anybody maybe who has an understanding of the technical implications? As I mentioned, my device receives the notifications but the app doesn't post them for whatever reason

11-19 15:23:08.289 net=1: Received com.x8bit.bitwarden
11-19 15:23:08.409 net=1: Acked com.x8bit.bitwarden:0
11-19 15:23:08.413 net=1: Successful broadcast to com.x8bit.bitwarden (id= time=63ms priority=NORMAL
<!-- gh-comment-id:2485875172 --> @larena1 commented on GitHub (Nov 19, 2024): @SergeantConfused is there anybody maybe who has an understanding of the technical implications? As I mentioned, my device receives the notifications but the app doesn't post them for whatever reason ``` 11-19 15:23:08.289 net=1: Received com.x8bit.bitwarden 11-19 15:23:08.409 net=1: Acked com.x8bit.bitwarden:0 11-19 15:23:08.413 net=1: Successful broadcast to com.x8bit.bitwarden (id= time=63ms priority=NORMAL ```
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#95302
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?