GitHub login not working for Sanity projects - known issue?

26 replies
Last updated: Jan 28, 2021
I use github to login to all sanity projects i work on - today No logins are working. Is this a known issue?Same behavior across different versions of sanity studio.
AI Update

I can see from the Sanity Status page that all systems are currently operational, including Authentication. There are no active incidents reported for GitHub login issues today.

However, login issues with GitHub OAuth can happen for a few different reasons. Here are the most common causes and troubleshooting steps:

The most common cause of GitHub login failures in 2025 is third-party cookies being blocked. Chrome and other browsers have been phasing out third-party cookies, which can break OAuth flows:

  • Check your browser settings: Ensure third-party cookies are allowed, at least for sanity.io and github.com
  • Try a different browser: Test in another browser or incognito/private mode to rule out browser-specific issues
  • Clear cookies and cache: Sometimes stale authentication cookies cause problems

Checking Service Status

Since you're experiencing this across multiple projects and Studio versions, I'd recommend:

  1. Check the Sanity Status page for any ongoing incidents (currently showing all green)
  2. Check GitHub's status page to see if there are any OAuth-related issues on their end
  3. Try alternative login methods: If you have Google or other providers configured, try those to rule out Sanity-specific issues

Recent Authentication History

Looking at the status page history, there was an authentication-related incident on October 20, 2025, but nothing recent. The Authentication component currently shows 100% uptime over the past 90 days.

Next Steps

If the issue persists after checking browser settings:

  • Try accessing Sanity Studio from a different network (mobile hotspot, different WiFi)
  • Check your browser's developer console for specific error messages during login
  • Contact Sanity support with details about the error messages you're seeing

Since this is affecting all your projects across different Studio versions, it's most likely a browser/cookie issue rather than a platform-wide outage. The third-party cookie changes in modern browsers are a known cause of OAuth login problems in 2025.

Show original thread
26 replies
I just logged out and was able to log back in without issue. When you log in are you just getting returned to the auth screen? If you’re in Chrome, I’ve had that happen on multiple services in the past (though always with G Suite auth). Part of the reason I switched to Firefox.
user A
Yup - just a redirect straight to the auth screen each time. Also I am on Firefox already 🙂
A fun note - I can log into teams using github just fine, just not individual studios.
Interesting. FWIW, I get that test cookie warning too (even when successfully logged in).
hm. Going to check out chrome - see if I get a different.Just cleared everything - ran through the github auth again and same behavior.
Hm, works fine in chrome. Odd - literally was loggin in and working yesterday 🙂
(i really dont want to use chrome)
What if you revoke your Firefox session in GitHub then log back in?
Oh good point. Let me try that
I have no idea how to do that 😅
You’ll have to go in Chrome to revoke the Firefox session, I think.
👍 Unfortunately no change
I will begrugingly use chrome today
Shoot.
Appreciate the help 🙂
No problem. Hope it works itself out soon.
An idea from
user P
- have you recently installed any browser plugins like Privacy Badger that might be interfering?
Thanks
user M
I have not added anything new - I do run strict tracking and private windows by default on firefox - so that probably has something to do with it.Whats odd is I have not changed my setup for over a year and its been running the same until today.
Would be interesting to see if less strict tracking allows you to login successfully, if that's within scope to try I mean.
Oh yea 100%. I will give that a shot here.Whats interesting to me is I can get into the teams portal with github auth just fine, but not studios.
user M
Issue resolved. I’ll just switch to standard mode when Im accessing sanity. Would be interested to know what changed between yesterday / today though. I recognize this is more of an edge case.
Oh workaround - I just do custom and enable only cookies 🙂
Great! Thanks for confirming. Regarding the teams portal vs. studios, I think that's because they're not 3rd-party cookies on the teams portal.
Glad you found that workaround too. Would be handy if you could set that on a site-level?
🙂 We'll still look into this issue to figure out why it changed. Will share any additional info with you but may take some time if so.
Of course - and got it, that makes sense.
This is 100% not a blocker, I was more interested to see if / what had changed.
Thanks for checking in / providing feedback

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?