Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fitness Trend page stuck in "loading" state #548

Closed
dee-see opened this issue Mar 16, 2018 · 3 comments
Closed

Fitness Trend page stuck in "loading" state #548

dee-see opened this issue Mar 16, 2018 · 3 comments

Comments

@dee-see
Copy link

dee-see commented Mar 16, 2018

Step 2: Describe your environment

  • Plugin version: 6.0.2 Stable
  • Chrome/Opera/Chromium version: Chromium 65.0.3325.162 (Developer Build) (64-bit)
  • OS version: Arch Linux, 4.15.8 kernel

Step 3: Describe the problem:

I don't have whatever is required to calculate fitness data and the page is forever stuck in loading mode.

Steps to reproduce:

  1. Open the fitness tab

Actual Behavior:

The "loading" indicator stays on screen forever with the following message in the console:

0.5b569a3e3a20ec953891.chunk.js:1 No activities has minimum required data to generate a fitness trend
(anonymous) @ 0.5b569a3e3a20ec953891.chunk.js:1
t.invoke @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
onInvoke @ main.848fdb43d2c619ccee5f.bundle.js:1
t.invoke @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
e.run @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
(anonymous) @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
t.invokeTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
onInvokeTask @ main.848fdb43d2c619ccee5f.bundle.js:1
t.invokeTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
e.runTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
d @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
Promise.then (async)
v @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
t.scheduleTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
onScheduleTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
t.scheduleTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
e.scheduleTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
e.scheduleMicroTask @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
P @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
S @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
(anonymous) @ polyfills.967fe5e6c57e15a99b6d.bundle.js:1
(anonymous) @ main.848fdb43d2c619ccee5f.bundle.js:1
safeCallbackApply @ extensions::uncaught_exception_handler:27
handleResponse @ extensions::sendRequest:67

Expected Behavior:

Empty graph/table, ideally with a message saying why.

@thomaschampagne
Copy link
Owner

@dee-see Could you provide me a backup of your history?
So i can reproduce and fix your problem. Thanks !

@dee-see
Copy link
Author

dee-see commented Mar 16, 2018

@thomaschampagne https://www.dropbox.com/s/dmk8z74m6k8b4lv/2018.3.16-12.13_v6.0.2.history.json?dl=0

Let me know when you picked it up please, I will delete the file.

@thomaschampagne
Copy link
Owner

@dee-see You can remove your link.

The bug is that there is no good displayed message for your case.

In fact, your history is not supported by this feature:

The fitness trend requires an athlete history with at least:

  • Heart rate data coming from an heart rate monitor and regardless types of sports.
  • Or power data coming a cycling power meter (or emulated power data such as "ZWIFT" sessions).
  • Or any swimming activities having distance & time (no sensors required). For this make sure you have set your Swimming Functional Threshold Pace in athlete settings.

Hope this helps,

Tom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants