Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Linking with Stack Exchange gives error "couldn't parse client_id"

Post

Linking with Stack Exchange gives error "couldn't parse client_id"

+4
−0

Problem:

I see the following error when I link my account with StackExchange:

Couldn't parse client_id

How we got here:

  • I click on my profile picture -> Click Edit -> Scroll down to Link with Stack Exchange -> Click Authenticate -> Enter my Stack Exchange login credentials.

Preliminary analysis:

I confirmed that my Stack Exchange login credentials are correct as follows:

  • I opened a private browsing window, logged in to my codidact account, then followed the above steps.
  • In the same window (and actually the same tab), I opened stackoverflow.com after getting the above error, and I was already logged in.

Additional information:

  • OS: Windows 10 64-bit
  • Browsers:
    • Brave: Version 1.7.98 Chromium: 81.0.4044.113 (Official Build) (64-bit)
    • Firefox: 73.0.1 (64-bit)
  • My account on Stack Overflow is "temporarily suspended".
History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (7 comments)
General comments
Monica Cellio‭ wrote about 4 years ago

Are you doing this here on Meta, or on one of our other sites (Writing or Outdoors)? I'll have to check, but it might not work on Meta because we don't have an associated SE site that we want to import posts from -- but if that's the case then we should have a better response than this error, so thanks for the report.

Masked Man‭ wrote about 4 years ago

@Monica It seems that was the issue here. I tried linking on this Meta site, since I don't have any content on Writing and Outdoors anyway. It would seem graying out the Authenticate button on this Meta site would be appropriate with an indication of why.

Monica Cellio‭ wrote about 4 years ago

@MaskedMan not your fault; we just added that "don't post here" language because the software made it too easy to end up here. Every other site we set up will have a meta, so it's baked in for now, but Meta doesn't need a meta...

Masked Man‭ wrote about 4 years ago

@Monica I realized what might have happened. When I saw the error, I first searched here to see if the problem is already reported. I came across this post https://meta.codidact.com/questions/39514. This was similar to my issue, but not the same. This question was on "meta meta" at the time (I think, don't remember clearly), and on that page, the link still read "Ask Question", so I used that.

Masked Man‭ wrote about 4 years ago

I know this is still early days, this is still a small community (and most of them are SE veterans anyway), so this "Don't Post Here" is ok for now. However, the "meta meta" site eventually needs to go if it isn't meant to be used. [It is probably already in the plan, I'm still feeling my way around here. :-)] Hopefully the community will grow to an extent where new users (with no knowledge of SE) will join, and this UI will be confusing even more than it is to the SE veterans.

Monica Cellio‭ wrote about 4 years ago · edited about 4 years ago

The "meta meta" page is going to go away, yes. We just need to make sure we've removed all the pre-category code that assumed that every site has a meta -- don't want to break this site in the process of yanking that out.

Masked Man‭ wrote about 4 years ago

Understood. I imagined it was something like that. I think that's fine for now.