Skip to main content
Solved

Plugins possibly behaving differently across different license types?

Michal_Kovacik1

Hello everyone,

there has been a few reports of my plugin https://www.figma.com/community/plugin/1404783727338541788/infinite-variable-modes not working for some users (it runs, shows some UI, but fails either at fetching variable collections, or at messaging between the UI and the part making calls to Figma plugin API), and it seems to have something to do with the type of plan(license) the user has. As far as I know, it should work fine on Free and Pro, but seems to struggle on Org and Enterprise. I was able to do a little testing with one of the users (Enterprise), who had an issue with the plugin, and as soon as he switched to his personal account (Free or Pro, not sure), it worked just fine. I wasn’t able to identify any other differences between the users for whom it works, and for whom it does not.

Have anyone experienced something like this before? Either from the user or the developer perspective?

Could there be some sort of settings in these Org and Enterprise plans, that could cause this? For one Org user it stopped working after few days, whilst he is not aware of any changes at his side.

Could it be something else, outside of Figma, that is common for corporations and could affect this? Like some security network stuff for example?

May I kindly ask you to try to run the plugin, and give me a feedback, whether it’s working or not, together with your plan type, and possibly a look into your console (CMD + OPTION/ALT + i) in case it doesn’t work?

Thank you all in advance.

Michal

Best answer by Michal_Kovacik1

Hi ​@y_toku ,

thank you very much for responding. Just a few hours ago I found the cause of the issue and was able to fix it.

In case it would help anyone, here’s what was going on:

It had nothing to do with the license type after all. Although the issue had been reported by users with Org and Enterprise plans, it was just a bias and a completely unrelated thing was happening there. The issue occurred inside files, that are published as libraries, because when you load local collections and team library collections in such file, you’ll essentially get the same collections twice. The team library collections simply overwrote the local ones in my plugin data, and therefore the UI had nothing to display, because it’s supposed to show only the local collections in that particular place of the plugin.

 

View original

3 replies

y_toku
Figmate
  • y_toku
  • Community Support
  • 2312 replies
  • March 18, 2025

Hi ​@Michal_Kovacik1, 

 

Thanks for reaching out. If you're seeing differences on the user’s side, I could come up with two possible cases:

  1. For organizations or Enterprise plan users, admins can restrict access by requiring approval before certain features can be used. In this case, some users may have accessed the plugin before this admin approval was implemented. Ultimately, this setting determines whether users have access, so it may not be the case.

  2. Some differences are related to the plan itself. For example, a Starter Plan user is limited to three pages in a Figma design file, and the Plugin API reflects this limitation (https://www.figma.com/plugin-docs/api/properties/figma-createpage/). The API mirrors the access restrictions of Figma products, which means it can’t provide Starter Plan users with features such as variables or Dev Mode. If your user is experiencing discrepancies between Starter Plan and paid plan users, this may be the cause.

Do you think one of the cases applies to your situation? I hope this helps but I’m also interested in how other users see this plugin behavior across plans.

 

Thanks,

Toku

Michal_Kovacik1
  • Michal_Kovacik1
  • Author
  • New Participant
  • 11 replies
  • Answer
  • March 18, 2025

Hi ​@y_toku ,

thank you very much for responding. Just a few hours ago I found the cause of the issue and was able to fix it.

In case it would help anyone, here’s what was going on:

It had nothing to do with the license type after all. Although the issue had been reported by users with Org and Enterprise plans, it was just a bias and a completely unrelated thing was happening there. The issue occurred inside files, that are published as libraries, because when you load local collections and team library collections in such file, you’ll essentially get the same collections twice. The team library collections simply overwrote the local ones in my plugin data, and therefore the UI had nothing to display, because it’s supposed to show only the local collections in that particular place of the plugin.

 

y_toku
1 person likes this
  • y_toku
    y_toku
y_toku
Figmate
  • y_toku
  • Community Support
  • 2312 replies
  • March 19, 2025

Thanks for the details ​@Michal_Kovacik1 ! It is really helpful for others. Really appreciate you shared! 

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings