Component not changing in prototype [BUG?]

I am having the same issue. Components that were previously transitioning to states (hover ie) are now not working correctly.

What has changed since? We upgraded to Org pricing tier.

Hello @tank666, do you know why this is happening? 🙂

Did it work properly before? If so, please submit a bug report to support.

Try removing the button component’s text property. Or create and use a new component that meets the requirements of this task.

I have tried the following with no success.

• create a new component
• Reload tabs / all tabs
• Restart Figma
• Restart computer.

Could you share a link to an example file?

I am facing the same issue but I don’t even have a hover effect. what’s going on? I am just changing the orientation of a triangle when clicked on the triangle should go from horizontal pointing to downward pointing. every other clickable component is working just fine.

I’m experiencing a similar issue just not with the text changing. But I have a pagination component made out of our button component. That button component has hover states that are wired up in the parent component to appear in any prototype (I’ve tried it with “Hover” and “Mouse Enter/Leave” to get it to work). Those buttons in my pagination component have different states depending on the state of the pagination component. When I test the component, pressing the arrow button or pressing the a number button to change to the next page I have a similar problem. Basically, which ever button is pressed looses the ability to change to the state/appearance it should be when the component “changes pages”. When I use the arrow buttons, they can’t appear as “disabled” when the pagination has hit 5. When I click the numbers then they can’t appear as the blue “active” when on that page in the component. It won’t let me upload a little video demo so here’s the little prototype link: https://www.figma.com/proto/7mV72zChjzIXlNjdnSchz8/Pagination-Problem-Trial?page-id=0%3A1&type=design&node-id=0-279&viewport=-568%2C-432%2C1.72&t=1sPN0Tt0EVhnrmSs-1&scaling=min-zoom&starting-point-node-id=0%3A279&mode=design

Hey @Sarah_Lund1, I tested your prototype and I think it’s related to this post:

Could you try applying the “Reset component state” setting?

Thank you! I had not found that thread yet when I was researching my problem. That worked and it’s changing states no problem now.