standardnotes / forum

Support from other community members. For 1-on-1 help, please contact help@standardnotes.com.
https://forum.standardnotes.org
198 stars 9 forks source link

Webapp - Sync error: The provided access token has expired #3715

Open dennisstewart opened 3 weeks ago

dennisstewart commented 3 weeks ago

Describe the bug I use the Standard Notes Android app and the webapp on Firefox. I noticed that changes I'm making are not being synced between these two. In the bottom right corner of the webapp, there is a note "Sync error: The provided access token has expired." Refreshing the page does not correct this issue. I am worried about losing the changes I've made if I try logging out and back in.

To Reproduce Steps to reproduce the behavior:

  1. Create a new note or edit an existing note
  2. The sync indicator in the upper-right will spin, and then show an error: Sync Unreachable, Changes saved offline

Expected behavior The application syncs, or displays instructions on how to get a new access token.

Screenshots image

image

Desktop (please complete the following information):

dennisstewart commented 3 weeks ago

As a note, the mobile app is syncing fine. If I log into Standard Notes from a Chrome incognito window, it can synchronize properly with the mobile app.

daboross commented 1 week ago

Hi! I also experienced this starting early August. (earliest unsynced note seemed to be from August 17th for me, though I don't write notes every day on my laptop)

I fixed it, or at least worked around the issue, by changing my password, to force a token refresh.

I couldn't do so on the browser - changing the password there ran into the same issue. So, I changed it in the android phone app. That prompted a sign in prompt in my browser session immediately.

After entering my email and new password into my existing bad browser session, it started syncing again, and all the notes that were previously missing / only present locally on my browser synced. Nothing lost.

dennisstewart commented 1 week ago

Thank you @daboross ! I can confirm your fix worked for me. I'll leave this issue open because I hope the developers can fix the underlying issue.