# Paring token changed after latest windows update?

**URL:** <https://bisq.community/t/paring-token-changed-after-latest-windows-update/11521>\
**Category:** Uncategorized\
**Created:** [April 28, 2022, 5:11pm UTC](https://bisq.community/t/paring-token-changed-after-latest-windows-update/11521 "2022-04-28T17:11:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Badha5h](https://bisq.community/letter_avatar/badha5h/32/5_5575768a8748004e209b776fc1b2916d.png) [@Badha5h](https://bisq.community/u/Badha5h)\
**Post date:** [April 28, 2022, 5:11pm UTC](https://bisq.community/t/paring-token-changed-after-latest-windows-update/11521/1 "2022-04-28T17:11:50Z")

</div>

Anyone else noticed they are no longer getting notifications on mobile?  
I stopped getting notifications after the latest update so I had to sync it again with a different code.

Kinda weird!??

---

<div class="post-metadata">

**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\
**Post date:** [April 29, 2022, 9:53am UTC](https://bisq.community/t/paring-token-changed-after-latest-windows-update/11521/2 "2022-04-29T09:53:36Z")

</div>

We might have been getting more reports like yours. We will look at it.

---

<div class="post-metadata">

**Author:** ![Droidus](https://bisq.community/letter_avatar/droidus/32/5_5575768a8748004e209b776fc1b2916d.png) [@Droidus](https://bisq.community/u/Droidus)\
**Post date:** [May 11, 2022, 12:29pm UTC](https://bisq.community/t/paring-token-changed-after-latest-windows-update/11521/3 "2022-05-11T12:29:59Z")

</div>

I am getting notifications but I can’t see their contents… I created an issue on Github about this

---

<div class="post-metadata">

**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\
**Post date:** [May 12, 2022, 6:15am UTC](https://bisq.community/t/paring-token-changed-after-latest-windows-update/11521/4 "2022-05-12T06:15:31Z")

</div>

This is a known issue, the app has not been updated for a long time.
