Figma File Search fails to provide access to raycast

[Gareth71]

Extension

https://www.raycast.com/michaelschultz/figma-files-raycast-extension

Raycast Version

1.79.1

macOS Version

14.5

Description

I tried to link my Figma team to the Figma extension, I had to sign in via my browser and when I returned to raycast I had an error

Error:

FetchError: request to https://oauth.raycast.com/v1/token/qTlHR2nhUt2e07Ynlbw-T4ALSoDPrGnUZU4z1VsH-scRq-We8cI9RfPKJb9UfEau0bCVYIc0qtW5fOVJ0rtUwDN6KSg5d8XgR_wRofMYARLRzAWhTb5mFsXTdFZl3GPQfA failed, reason: unable to get local issuer certificate

    at withAccessToken(A5)
_r:index.js:8:2593
    at ray-navigation-stack
Eo:index.js:8:2094

Steps To Reproduce

With above raycast and macOS Select "Search Files" command from Figma extension In Connect your Figma account screen click Sign in with Figma In this screen

Click allow access In this screen

click open to raycast (I had to use button chrome provided rather the one in the webpage) See this screen

Current Behaviour

see error message

Expected Behaviour

Figma account would be linked and would be able to search files

[raycastbot]

Thank you for opening this issue!

🔔 @michaelwschultz @pernielsentikaer @GLaDO8 you might want to have a look.

💡 Author and Contributors commands

The author and contributors of `michaelschultz/figma-files-raycast-extension` can trigger bot actions by commenting: - `@raycastbot close this issue` Closes the issue. - `@raycastbot rename this issue to "Awesome new title"` Renames the issue. - `@raycastbot reopen this issue` Reopens the issue. - `@raycastbot assign me` Assigns yourself to the issue. - `@raycastbot good first issue` Adds the "Good first issue" label to the issue. - `@raycastbot keep this issue open` Make sure the issue won't go stale and will be kept open by the bot.

[michaelwschultz]

@Gareth71 thanks for reporting. Have you also added your team ID in the extension settings?

Appreciate the in-depth report btw. I think a few of the small bugs you ran into are Raycast issues and I'll pass them along.

[Gareth71]

Yes, I added my teams id following the instructions I found from a website I googled (see below). I checked and I can see it in the extensions settings.GarethOn 20 Jul 2024, at 5:56 PM, Michael Schultz @.***> wrote: @Gareth71 thanks for reporting. Have you also added your team ID in the extension settings? Appreciate the in-depth report btw. I think a few of the small bugs you ran into are Raycast issues and I'll pass them along.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[chrisd008]

I'm having the same issue. After entering the team ID, clicking "sign in with figma" button, and then allowing access, I just get the "something went wrong" message. If I had to guess there may be an issue with our Figma SSO / security settings that is preventing this from working. Even as a Figma admin in my org I don't see a way to add Raycast to the "connected apps" list within Figma's settings.

I've also tried the personal access token path and this results in the extension no longer giving me a "something went wrong" message, but rather the "Could not load files" message in the bottom left, along with "No Results" empty state. There is clearly something getting hung up and I have to assume it has something to do with our security settings, but I've got no idea how to address and resolve the issue (or if it just isn't possible).

[michaelwschultz]

@thomaspaulmann mind weighing in here?