-
Notifications
You must be signed in to change notification settings - Fork 177
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
[Web-Ext][Bug] Year Progressions screen broken #1212
Comments
@mvanhulsentop , quick question, if you don't mind: do you by any chance have multiple users in Chrome? I'm asking because I used to have Elevate under one user, then installed the app in another user and I suspect that broke things... I have since removed the second user and I'm currently re-syncing everything again to see if it fixes the issue. |
@MLocria yes, this indeed the case, i have a work profile and a personal profile. Elevate is only running in my personal profile. |
So, I can confirm that I now see the graphs above correctly. @mvanhulsentop , if you can confirm it's the same for you, then maybe we team can find a way to fix this when priorities allow for it. Thanks! |
You need to perform a full resync using version 7.2.1 :/ Did you do that? |
Hi @thomaschampagne ! Yes, I seem to remember that I:
If you want, I can re-add the second Chrome user and see if I can replicate the issue once more. It'll take me a few days, due to Strava's limits. Let me know! |
With version 7.2.1, i can now confirm the progression screen is functioning again. Thank you @thomaschampagne ! |
Describe the bug
The Year Progressions screen has not loaded correctly at least since Oct 26th (last screenshot I took).
To Reproduce
Expected behavior
Show the Year Progressions screen.
Screenshots
(1) Latest screenshot I took with the app working
(2) Screenshot of the issue today
Environment
Additional context
Thanks for the awesome product, I hope this is solvable! Hopefully, something stupid on my end 😅 Let me know if I can provide more info!
The text was updated successfully, but these errors were encountered: