Code Connect error trying to install my GitHub repo

Hey ​@Fernando7 — welcome to Figma Forum, and thanks for flagging this!

I just checked GitHub’s status page, and everything looks operational. Are you still running into the same error? In most cases, when the “Something went wrong” error message appears, a quick tab reload and retry usually resolves it.

If the issue persists, and you’ve already tried reloading and connecting another repository without any problems, I’d recommend reaching out to our Product Support team so they can take a closer look at your specific setup. When you reach out, please include:

• the link to this Forum thread for context
• a full-size screen recording of the issue (if possible)
• a link to the affected Figma Make file
• make sure support-share@figma.com has Can edit access.

I will keep a lookout for other reports and return with any other solutions as well. Keep us posted on how things go — and don’t hesitate to share any updates here in the thread so others can benefit too.

Hey ​@Tom Reem, I tried many times with the reload button, but with no success.

I got the error while using Safari browser - Version 26.0.1 (21622.1.22.11.15).
I tried using Google Chrome and it worked.

Compatibility problem or bug?

Thanks!

Hey ​@Fernando7 — really appreciate the update and the extra troubleshooting you’ve done. Great call testing in Google Chrome. That helps confirm the issue is likely environment-specific — sorry for the continued friction in Safari.

To help us isolate what’s happening, could you share a bit more detail when you have a moment?

• Can you confirm you have a Dev or Full seat within an Organization or Enterprise plan?
• When was the last time you successfully connected your GitHub repository via Safari, and have there been any changes to your setup since then (e.g. a different account login, browser extensions, or cache settings)?
• Could you outline the exact steps leading up to the error or share a short screen recording if that’s easier?

This will help us narrow down whether we’re looking at an auth session or browser-level issue. Thanks again for the thoughtful troubleshooting so far — I’ll keep an eye out for your reply and escalate once we have these details.