You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first sync seemed to work fine. I sorted one conflict I had and then deleted the fit folder. After this I started getting an "unable to sync error" (I've attached the screenshot for the full message, but it essentially relates it to the internet). I disconnected & then reconnected to my WiFi source and still got this issue. I then tried uninstalling & reinstalling this plugin (I'm thinking maybe this wasn't a good idea but alas) in case it was the fit folder deletion that was the issue and that didn't work either.
Any suggestions?
(thank you by the way though)
The text was updated successfully, but these errors were encountered:
I have the same issue: on my Samsung S23 phone, the Fit sync works for the initial sync. Even without changing anything, all subsequent sync attempts fail with "Unable to sync" message. The console.log indicates a 403 response. The Personal Access Token is permissioned with full "repo" perms.
@joshuakto I have the same fit sync issue on my iPhone. Worked fine initially and I could also sync from my mobile device, but a couple of days ago stopped working
Is this happening only on mobile devices? Could we add a debug option to enable on the phone and check for errors?
The first sync seemed to work fine. I sorted one conflict I had and then deleted the fit folder. After this I started getting an "unable to sync error" (I've attached the screenshot for the full message, but it essentially relates it to the internet). I disconnected & then reconnected to my WiFi source and still got this issue. I then tried uninstalling & reinstalling this plugin (I'm thinking maybe this wasn't a good idea but alas) in case it was the fit folder deletion that was the issue and that didn't work either.
Any suggestions?
(thank you by the way though)
The text was updated successfully, but these errors were encountered: