From 2f2632c56c7cf72884bdcda9e22362b3c3619ba3 Mon Sep 17 00:00:00 2001
From: Nicolas Delahaie <91760731+Nicolas-Delahaie@users.noreply.github.com>
Date: Sun, 7 Sep 2025 18:56:12 +0200
Subject: [PATCH] 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.

---
 Enabling-Mobile-Client-push-notification.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Enabling-Mobile-Client-push-notification.md b/Enabling-Mobile-Client-push-notification.md
index eb86aff..664b6a9 100644
--- a/Enabling-Mobile-Client-push-notification.md
+++ b/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
 ```
 
-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]
 > 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).