philosowaffle/peloton-to-garmin

Periodic Sync not working - Windows

toquie opened this issue · 1 comments

Describe the bug
In the Home Tab I get the following error "Periodic syncing is Not Running".

In the Settings/App Tab I have turned on Automatic Syncing but still have the same error.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Home Tab'
  2. Click on nothing the error is right there.
  3. Automatic Syncing is on and I save it however if I reopen the app the Automatic Syncing is now off.

Expected behavior
It not to say Periodic Syncing is Not Running and P2G would be syncing daily (86400 seconds).

Logs

Paste Log output here

P2G Version: p2g_clientui 4.1.0
Operating System: Win32NT
OS Version: Microsoft Windows NT 10.0.22621.0
DotNet Runtime: 7.0.14
Docker Deployment: False
Config path: C:\WINDOWS\system32\configuration.local.json
*********************************************
2024-02-08 18:20:50.954 -08:00 [INF] *********************************************
2024-02-08 18:20:50.987 -08:00 [INF] P2G Version: p2g_clientui 4.1.0
2024-02-08 18:20:50.989 -08:00 [INF] Operating System: Win32NT
2024-02-08 18:20:50.989 -08:00 [INF] OS Version: Microsoft Windows NT 10.0.22621.0
2024-02-08 18:20:50.990 -08:00 [INF] DotNet Runtime: 7.0.14
2024-02-08 18:20:50.990 -08:00 [INF] Docker Deployment: false
2024-02-08 18:20:50.991 -08:00 [INF] Config path: C:\WINDOWS\system32\configuration.local.json
2024-02-08 18:20:50.991 -08:00 [INF] *********************************************

**Installation (please complete the following information):**
 - OS: WIN32NT 10.0.22621.0
 - Method: exe
 - Version: 4.10 (runtime version 7.0.14)

**Additional context**
Just going to mention this here but will create another ticket - P2G will not open or work when I run it other than open as an Administrator even though I am the administrator on my computer. 
<img width="431" alt="Screenshot 2024-02-08 182103" src="https://github.com/philosowaffle/peloton-to-garmin/assets/47252498/20aa4b68-abec-417e-a263-7217f0999773">

I've identified the root cause. Unfortunately the fix is not straight forward. I will have to do some additional research.