I can't connect strava

[Tony]

Good morning, I have been using GoldenCheetah for three years, for my team of 12 guys, it has always worked, now I am trying to insert the new arrivals, but when I go to "add account for cloud - activities - strava" I click on the strava banner, I insert the credentials, the response is always An unexpected error occurred. Try again. The credentials entered directly on the strava site work. I tried with versions, 3.5, 3.6 and also 3.7 N.B. the athletes already registered at the beginning of 2024 download without problems Can you help me understand what is happening Thanks

[Ale Martinez]

I can’t reproduce this using latest snapshot build.

 You could start GC from a command line/terminal with —debug option to see if other errors are reported there.

[ZajtiM]

I had my account (strava) already connected. But i wanted to check something, so i removed it in GC and removed / revoked access in Strava.
And when i wanted to add Strava in GC i get the same "error" in OAuth window (Login form).

Here is my debug:
/XTRA/APPs/GoldenCheetah_v3.7-DEV_x64.AppImage --debug
[18:01:26.682] info: Sandboxing disabled by user.
[18:02:12.347] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:12.468] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
[18:02:33.324] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:33.496] warning: [Meta Pixel] - Removed URL query parameters due to potential violations.
[18:02:44.209] warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21756, resource id: 9669832, major code: 40 (TranslateCoords), minor code: 0
[18:02:44.210] warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21774, resource id: 9675789, major code: 40 (TranslateCoords), minor code: 0
[18:02:54.553] warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21881, resource id: 9674330, major code: 40 (TranslateCoords), minor code: 0
[18:05:34.539] warning: QXcbClipboard: Unable to receive an event from the clipboard manager in a reasonable time


"
18:02:12.347] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:12.468] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
"
these two lines are displayed when i accept cookies.

"
[18:02:33.324] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:33.496] warning: [Meta Pixel] - Removed URL query parameters due to potential violations.
"
And this is when i successfully authenticated (i don't know how / why, because now is not working again).  :)

I wanted to test a bit more, so i removed my Strava again (in GC and Strava website). And now i'm not able to authenticate again.
So all i see when in debug is this (on repeat), if i want to auth my account.
"
18:02:12.347] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:12.468] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
"

Btw, i sort of don't care if i can't connect / auth my account at the moment. I'm just posting my debug "results".

I was "testing" this with Oct 26 build and latest Dec 14 build. And i'm using AppImage in Linux Mint.

[Ale Martinez]

El martes, 31 de diciembre de 2024 a la(s) 4:27:00 p.m. UTC-3, ZajtiM escribió:

I had my account (strava) already connected. But i wanted to check something, so i removed it in GC and removed / revoked access in Strava.
And when i wanted to add Strava in GC i get the same "error" in OAuth window (Login form).

Here is my debug:
/XTRA/APPs/GoldenCheetah_v3.7-DEV_x64.AppImage --debug
[18:01:26.682] info: Sandboxing disabled by user.
[18:02:12.347] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:12.468] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
[18:02:33.324] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:33.496] warning: [Meta Pixel] - Removed URL query parameters due to potential violations.
[18:02:44.209] warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21756, resource id: 9669832, major code: 40 (TranslateCoords), minor code: 0
[18:02:44.210] warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21774, resource id: 9675789, major code: 40 (TranslateCoords), minor code: 0
[18:02:54.553] warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21881, resource id: 9674330, major code: 40 (TranslateCoords), minor code: 0
[18:05:34.539] warning: QXcbClipboard: Unable to receive an event from the clipboard manager in a reasonable time


"
18:02:12.347] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:12.468] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
"
these two lines are displayed when i accept cookies.

"
[18:02:33.324] warning: Unrecognized feature: 'attribution-reporting'.
[18:02:33.496] warning: [Meta Pixel] - Removed URL query parameters due to potential violations.
"
And this is when i successfully authenticated (i don't know how / why, because now is not working again).  :)

It seems to be a hit-and-miss situation, my initial test worked in the first attempt, now tried again and the first 2 failed and the 3rd worked, I don't see a pattern in the warnings either. 

[Tony]

Sorry, how do I launch the debug, I can't do it.
Thanks

[ZajtiM]

Hey Tony,

If you read all replies in this thread, you can see, you won't be able to find out anything with "--debug". It looks like something is wrong on Strava side. Ale and i tried debug mode and nothing shows up.

But in case you still want to try debug mode. This is how you do. You have to start GC from terminal but at the end you add "--debug". Just copy everything between both ".

It is fairly simple thing to do. But if you don't know how to start app from terminal, just google it.

Just for your info. I had problem authenticating my account whole weekend, since i removed it for the second time. Still not working for me.

[Ale Martinez]

At the troubleshooting section of the wiki there are Instructions to start GC from a command line or terminal window.

As explained above, the problem seems confined to the Strava authentication step, you can retry in that same window as indicated by the error message, when and if it eventually succeeds, the authorization step works as expected. 

[Tony]

sorry but golden cheetah which method does it use to request the token the old v2 method or the new v3. I understand that the old v2 method gave this problem.

[Mark Liversedge]

On Sunday, 5 January 2025 at 08:50:40 UTC Tony wrote:

sorry but golden cheetah which method does it use to request the token the old v2 method or the new v3. I understand that the old v2 method gave this problem.

We switched to v3 in 2017 

[ZajtiM]

I just tried to connect / authenticate my Strava again (first time today - 14:25 CET) and it worked with first try. After trying every day, since it didn't work.
Then i disconnected / revoked it again and tried to connect it again. It didn't work second try. But right after that it worked again.

So i think Strava fixed whatever was the issue. Posting this just for extra info if needed.

[Tony]

I tried starting like this D:\Golden_Cheetah\Golden Cheetah\GoldenCheetah.exe -debug usage: GoldenCheetah [[\\d:gc] alan] Then going to the Strava connection section it worked for all 10 of my athletes. I know it doesn't make sense, but it worked. HI I tried starting like this D:\Golden_Cheetah\Golden Cheetah\GoldenCheetah.exe -debug usage: GoldenCheetah [[\\d:gc] alan] Then going to the Strava connection section it worked for all 10 of my athletes. I know it doesn't make sense, but it worked. HI

[David]

Just to add my two cents I don't think it's fixed yet, or at least I'm getting "unexpected error, try again" at the time of writing. 

[ZajtiM]

On Monday, 20 January 2025 at 05:47:22 UTC+1 David wrote:

Just to add my two cents I don't think it's fixed yet, or at least I'm getting "unexpected error, try again" at the time of writing.

It was definitely fixed when i posted about it, 11 days ago. And if it is not working again, nothing can be done on GC side. You will just have to wait for Strava to fix it.

[Joaquin López Sánchez-Montañés]

I'm running the Linux version (5002 compilation) with the debug option. The output when I put the e-mail address at the box is:

[20:34:47.346] warning: Unrecognized feature: 'attribution-reporting'.
[20:34:47.544] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
[20:34:54.509] warning: Unrecognized feature: 'attribution-reporting'.
[20:34:54.565] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.

Unexpedted error. Try again

[Mark Liversedge]

On Wednesday, 26 February 2025 at 07:59:51 UTC joaquin.lo...@gmail.com wrote:

I'm running the Linux version (5002 compilation) with the debug option. The output when I put the e-mail address at the box is:

[20:34:47.346] warning: Unrecognized feature: 'attribution-reporting'.
[20:34:47.544] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.
[20:34:54.509] warning: Unrecognized feature: 'attribution-reporting'.
[20:34:54.565] warning: [Meta Pixel] - Duplicate Pixel ID: 845436102209527.

Interesting (although its not relevant to your issue which is likely a local firewall or network issue)

Implementing the meta pixel in a login screen without cookie consent is considered illegal under the GDPR in the EU.

Mark 

[Joaquin López Sánchez-Montañés]

I'm not able to link my account with strava. It's not a networh problem.

When I try to configure it on the Authorize box and click on the strava button with the logo, the OAuth window appears, and after writing the e-mail and pushing the 'login in' button, an error appears: 'Unexpected error, try it again'.

I've done several tryings in Ubuntu, Windows 11, another network, and so on, and always appears this error.

Even with a lower version of the program.

Please, can anybody help me?

Thanks in advance!

[Ale Martinez]

El jueves, 6 de marzo de 2025 a la(s) 4:59:45 p.m. UTC-3, Joaquin López Sánchez-Montañés escribió:

I'm not able to link my account with strava. It's not a networh problem.

When I try to configure it on the Authorize box and click on the strava button with the logo, the OAuth window appears, and after writing the e-mail and pushing the 'login in' button, an error appears: 'Unexpected error, try it again'.

I've done several tryings in Ubuntu, Windows 11, another network, and so on, and always appears this error.

Even with a lower version of the program.

Please, can anybody help me?

Since you posted exactly the same as the OP (which also started creating a self-contradictory GitHub issue, BTW)  without providing any new information, I think there are 2 posibilities:

1) You read the previous posts but did not understand something on them

2) You did not take the time to read and understand them

If 1) please be more specific about what you don't understand, if 2) please do you part.

Thank you.

[scot]

I cannot comment on the GitHub or other situation, but I can confirm that in 3.6 the login button for email logins no longer works with Strava. Whatever javascript code they are using to look for a properly formatted email address does not work.  Upgrading to 3.7 beta (any of them) will allow the login button to work, but it will not allow a login and ends with "an unexpected error occurred" 

Debug logging mode does not provide the har file or other tracking of the actual web interaction between GC and Strava.  Is there a different string that can directly output the internal html browser? 

I attempted to login many times, *one* time it got me to the "are you sure you want to use passwords* screen (vs PIN code) but selecting anything there ended with an unexpected error occurred.  

So it definitely appears to be an issue within the GC browser and the oauth subsystem.  Is there a way to manually pull the token and refresh token via another browser session and place it into the athlete private ini file? 

1as for Ale's 1-2 questions, at no point is a solution given above.  One post talks about the error being on the strava side, but it does not appear to fully be on their side.  I *was* able to get it to work once, but since then I've tried ~100 times, randomly it will ask for captcha, which succeeds.  Network is clean without any blocking of any traffic.  Need a method to provide more detailed logs, as debug provides nothing extra that I can see (it doesn't seem to track the GC browser requests)

[Podium Performance]

Hi everyone, I am obviously less skilled at troubleshooting and my knowledge on how to do so or even report is non-existent.

However, here's how I managed to get 1 new athlete synced up. Here's the steps:
1. Create athlete as usual
2. Copy the athete-private.ini file from someone else and paste it inside the new athlete's folder
3. Open the .ini file - obviously the token belongs to the "someone else"
4. Instruct new athlete to sync their Strava with a Gmail address
5. Somehow on GC v3.6, we can log in to Strava via Gmail. Enter details and voila, the unique token for new athlete appears within the OAuth window.
6. Replace the token details of "someone else" with new athlete's

Hope FBI doesn't break my door down. I also hope this works for everyone.

Cheers

[Joaquin López Sánchez-Montañés]

Dear Ale, the only thing I understand after reading the previous posts is what ZajtiM said on 20/01/25:  'You will just have to wait for Strava to fix it.'

So, if this is the only solution, I'll wait some weeks to see if Strava fixes it.

I've tryed at least 5 times and the answer is always the same: 'Unexpected error. Try it again.'

Regards,

[Ale Martinez]

El viernes, 7 de marzo de 2025 a la(s) 12:25:18 p.m. UTC-3, scot escribió:

I cannot comment on the GitHub or other situation, but I can confirm that in 3.6 the login button for email logins no longer works with Strava. Whatever javascript code they are using to look for a properly formatted email address does not work.

macOS v3.6 build uses a now deprecated Qt version (5.14.2) so changing to v3.7 for anything related to the Web is recommended, for Linux and Windows versions there is no difference, all of them use still supported Qt5.15.

 

 Upgrading to 3.7 beta (any of them) will allow the login button to work, but it will not allow a login and ends with "an unexpected error occurred" 

That error happens at a point of the authorization stage where there is no GC code involved, only Strava code running on a Qt WebEngine window.

 

Debug logging mode does not provide the har file or other tracking of the actual web interaction between GC and Strava.  Is there a different string that can directly output the internal html browser? 

No

 

I attempted to login many times, *one* time it got me to the "are you sure you want to use passwords* screen (vs PIN code) but selecting anything there ended with an unexpected error occurred.  

So it definitely appears to be an issue within the GC browser and the oauth subsystem.  Is there a way to manually pull the token and refresh token via another browser session and place it into the athlete private ini file? 

No

 

1as for Ale's 1-2 questions, at no point is a solution given above. One post talks about the error being on the strava side, but it does not appear to fully be on their side.

Changes happened at their side and there is no GC code involved when the error happens, may be they changed the browser requirements, I tried using my local build with latest Qt 6.8.2 and it worked at the first attempt, so for users building from source that is something to try.

 

 I *was* able to get it to work once, but since then I've tried ~100 times, randomly it will ask for captcha, which succeeds.  Network is clean without any blocking of any traffic.  Need a method to provide more detailed logs, as debug provides nothing extra that I can see (it doesn't seem to track the GC browser requests)

Feel free to add what you need, source code is available at https://github.com/GoldenCheetah/GoldenCheetah/blob/master/src/Cloud/OAuthDialog.cpp, and you can use https://groups.google.com/g/golden-cheetah-developers if you want to discuss about that.

[Ale Martinez]

El viernes, 7 de marzo de 2025 a la(s) 4:00:23 p.m. UTC-3, Joaquin López Sánchez-Montañés escribió:

Dear Ale, the only thing I understand after reading the previous posts is what ZajtiM said on 20/01/25:  'You will just have to wait for Strava to fix it.'

So, if this is the only solution, I'll wait some weeks to see if Strava fixes it.

I've tryed at least 5 times and the answer is always the same: 'Unexpected error. Try it again.'

That's pretty much all we know, my point is just tiredly repeating the same error report is not useful at all, if you are a Strava customer perhaps you can try reporting to them for a change. 

[Ale Martinez]

El viernes, 7 de marzo de 2025 a la(s) 8:32:43 p.m. UTC-3, Ale Martinez escribió:

El viernes, 7 de marzo de 2025 a la(s) 12:25:18 p.m. UTC-3, scot escribió:

I cannot comment on the GitHub or other situation, but I can confirm that in 3.6 the login button for email logins no longer works with Strava. Whatever javascript code they are using to look for a properly formatted email address does not work.

macOS v3.6 build uses a now deprecated Qt version (5.14.2) so changing to v3.7 for anything related to the Web is recommended, for Linux and Windows versions there is no difference, all of them use still supported Qt5.15.

 

 Upgrading to 3.7 beta (any of them) will allow the login button to work, but it will not allow a login and ends with "an unexpected error occurred" 

That error happens at a point of the authorization stage where there is no GC code involved, only Strava code running on a Qt WebEngine window.

 

Debug logging mode does not provide the har file or other tracking of the actual web interaction between GC and Strava.  Is there a different string that can directly output the internal html browser? 

No

 

I attempted to login many times, *one* time it got me to the "are you sure you want to use passwords* screen (vs PIN code) but selecting anything there ended with an unexpected error occurred.  

So it definitely appears to be an issue within the GC browser and the oauth subsystem.  Is there a way to manually pull the token and refresh token via another browser session and place it into the athlete private ini file? 

No

 

1as for Ale's 1-2 questions, at no point is a solution given above. One post talks about the error being on the strava side, but it does not appear to fully be on their side.

Changes happened at their side and there is no GC code involved when the error happens, may be they changed the browser requirements, I tried using my local build with latest Qt 6.8.2 and it worked at the first attempt, so for users building from source that is something to try.

For Windows users not able or willing to build from source there’s an installer using Qt 6.8.2 available for testing from https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/snapshot

[Ale Martinez]

In v3,7 release page (https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/v3.7) there are Qt6 based builds for Windows and Linux, I tested Strava authorization and sync from scratch today, and both worked at the first attempt without errors.

[Ale Martinez]

El lunes, 7 de abril de 2025 a la(s) 11:07:39 p.m. UTC-3, Ale Martinez escribió:

In v3,7 release page (https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/v3.7) there are Qt6 based builds for Windows and Linux, I tested Strava authorization and sync from scratch today, and both worked at the first attempt without errors.

There is also a Qt6 based build for macOS available for testing now.

[Charles Moore]

Unfortunately, the problem is back.  

I recently did a new install of GC from the goldencheetah dot org site onto a new Windows 11 machine.  This installed GC V3.7 with build date Mar 29 2025 and build ID 5005.

I read through the above posts and didn't see any solutions other than wait, and a .ini profile workaround, which won't work for a single user with no other profile.

I wonder if it has something to do with Strava now offering the option to switch to a one-time code instead of using a password?  I'm still using the password method.  I wonder if this has something to do with it?

[ZajtiM]

Hi Charles. You can check my answer here.
https://groups.google.com/g/golden-cheetah-users/c/VoFDLg75OLw/m/1DTrwpuiAwAJ

It is from 19 Jun and i was also not able to connect. But i tried a few times i a row and then it let me connect. Like you said. It looks like this is going on since they switched to one-time codes. Other than that, you can't do anything to "fix" it as you have figured out.

[Charles Moore]

Thanks to this post for giving me inspiration to just copy my entire athlete folder from the old computer to the new computer.  This "fixed" my login error and GC is now syncing with Strava.

With the sunset of W10 support this could be a good option for users such as myself who have an existing install on another machine and are installing the latest GC on a new W11 machine.

[Alexsandro Santin]

Same here, can't connect to Strava

[Podium Performance]

Hey there, Version 3.7 works fine for me now (fingers crossed). There's a couple ways to do this

1. If you're like me who prefers to use an older version of GC. Have two laptops, created new athletes on Version 3.7 on one laptop and copy paste the individual's folder into the other laptop
2. I also tried putting the athletes folder on Google Drive as well, this works well and saves the trouble of copying and pasting. Bonus I can move between laptops regardless of GC version

Hope that helps!