code-connect icon indicating copy to clipboard operation
code-connect copied to clipboard

Code Connect "Something went wrong with the properties panel"

Open InsideRaptor opened this issue 6 months ago • 2 comments

Environment:

  • Code Connect: v1.3.4
  • OS: macOS 15.6
  • Framework: HTML/Web Components

Issue: Code Connect files publish successfully via CLI, but Figma Dev Mode shows "Something went wrong with the properties panel" error instead of displaying the connected code snippet.

Expected Behavior: Code snippet should appear in the Dev Mode properties panel after successful publish.

Actual Behavior: Properties panel shows error message (see screenshot below) despite successful CLI upload.

Image

CLI Output (appears successful):

Validating Code Connect files...
All Code Connect files are valid (3771ms)
Uploading to Figma...
Successfully uploaded to Figma, for React:
->  https://www.figma.com....node-id=14344-1718

Code Connect File:

import figma, { html } from '@figma/code-connect/html'
figma.connect(
  'https://www.figma.com....node-id=14344-1718',
  {
    props: {
      size: figma.enum('size', { large: 'large', medium: 'medium', small: 'small' }),
    },
  example: ({ size }) => html`\
<vds-button size=${size}>
  Button
</vds-button>`
})

Additional Context:

  • Node ID points to component set (not variant)
  • Multiple refreshes of Figma don't resolve the issue
  • Both code repository and Figma file are behind VPN/private access
  • Tested on both Figma desktop app and web browser with same results
  • Other team members are experiencing the same issue

Reproduction:

  • Create HTML Code Connect file
  • Run npx figma connect publish
  • Navigate to component in Figma Dev Mode
  • Observe error message in properties panel instead of code snippet

InsideRaptor avatar Aug 19 '25 20:08 InsideRaptor

Hello! Do you happen to see anything in the console of the browser when you see this issue?

We managed to get it working with the correct html parser, it was some config issue. But now, after i while, it randomly stopped showing it with no new code changes, and we are back on the error message.

Here is a screenshot of the console, a lot of connection errors and some other ones Image

.txt file with more logs console_logs.txt

InsideRaptor avatar Aug 20 '25 19:08 InsideRaptor