Check Switching to other Zeplin accounts to learn more about authenticating with another account.
If you're a part of a workspace, the role of the Zeplin account must be Developer or higher.
If you are getting permission errors regardless of your role, please check that if your account joined to the project or the styleguide that you are trying to connect.
The plugin you are using could not parse or find a definition of a component. This is a common issue for React component as there are many ways to compose a component and some of these methods are not supported by react-docgen or react-docgen-typescript. Please check React plugin documentation for details.
Storybook integration uses the same infrastructure as Connected Components. Using both at the same time may cause CLI to overwrite the latest changes made using the Storybook integration.
If the latest change is made with the Storybook integration on Zeplin apps, executing zeplin connect command prints a warning message and exits to prevent a possible overwrite.
You may use --force flag to enforce the overwrite operation on Zeplin CLI.
Please check the support article to learn more about Zeplin Storybook integration.
Please see the Matching components with stories document.
This can happpen when you are using Storybook v5+ but the links are not generated using v5+ format. To resolve it please see the URL format for manual matching document.
This can happen if the Storybook instance is served over HTTPS with a self-signed or an intermediate certificate. Currently we don't support custom certificates to connect Storybook but you can configure Storybook plugin to ignore SSL errors.
Please see the Using Basic Authentication document.