Missing component tokens on v0

v0 add to codebase does not include token anymore and this leads to error:

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

You are not authorized to access the component at https://v0.dev/chat/b/xxxxxxx/json.
If this is a remote registry, you may need to authenticate.

1 Like

Hi, Ubeyt! Welcome to the Vercel Community :wave:

Could you try making the chat public and adding the component to your codebase again?

Hey Pauline,
If it’s public, why does it need a token? The token is for authentication purposes, right?
I also don’t want to make it public.

I am facing issue adding to codebase (VS Code terminal) as shown. seek advice pls. tk u.

Hey, @el2060!

I moved your post to this discussion as it’s the same question.

@ubeytdemir4se-gmailc I was wondering if that would fix it as I’d seen it before, but you’re right this isn’t expected behaviour - let me check in with the v0 team and loop back!

2 Likes

Thanks Pauline!

I’m sure they will handle in no time.

I’m having the same issue.
I was able to workaround this by setting sharing to unlisted:

1 Like

Hey everyone! The team just shipped a fix. Can you confirm it’s working for you now?

@jeffstaylor120 @ubeytdemir4se-gmailc @el2060

2 Likes

Yes it works , thanks Pauline and v0 team!

2 Likes

Great to hear! Thanks again for your patience. :smile:

See you around the community :wave:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.