rhino/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-26 03:39:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

I made this change after solving the problem. Note that Bitwarden mobile does not automatically re-register itself: you need to log out and log back in.

Nicolas Delahaie
2025-09-07 18:56:12 +02:00
parent ccf2c2a611
commit 2f2632c56c
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
Enabling-Mobile-Client-push-notification.md

@@ -24,7 +24,8 @@ Since version `1.29.0` of Vaultwarden, you can activate Mobile Client push notif
docker compose up -d vaultwarden docker compose up -d vaultwarden
``` ```
4. Connect your app to your Vaultwarden instance. 4. Log out and log back in your Bitwarden mobile app so that the device re-registers its push token with the server.
> [!WARNING] > [!WARNING]
> If you have already connected your Bitwarden app before [v1.30.2](https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.2) push notifications **will not work** for your device (because the device token was never saved). You have to **clear the app data** of your mobile app (or **reinstall the app**) and connect your Vaultwarden account again to register the push token with [Bitwarden's Azure Notification Hub](https://contributing.bitwarden.com/architecture/deep-dives/push-notifications/mobile/#self-hosted-implementation). > If you have already connected your Bitwarden app before [v1.30.2](https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.2) push notifications **will not work** for your device (because the device token was never saved). You have to **clear the app data** of your mobile app (or **reinstall the app**) and connect your Vaultwarden account again to register the push token with [Bitwarden's Azure Notification Hub](https://contributing.bitwarden.com/architecture/deep-dives/push-notifications/mobile/#self-hosted-implementation).