[Bug]: Still happening in Storybook 7.4.0: "Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'count')"

[jasosims]

Describe the bug

This bug (previously reported in #23787) was marked as fixed, but is still happening in Storybook 7.4.0.

To Reproduce

1. Go to any story for a component with an on[Something] handler that's tracked by the Actions addon.
2. Reload the page.
3. Perform an action (for example, if the component has an onClick prop, click it).

Same error as before. Not fixed. This has been happening since Storybook 7.2.0. The only workaround is to downgrade to Storybook 7.1.1.

System

No response

Additional context

No response

[vanessayuenn]

@jasosims are you able to share a repro in 7.4? I can reproduce the issue easily with 7.2.1 and confirm upgrading to 7.4.0 made it work again.

If you haven't yet, could you also try clearing node_modules and reinstall?

[daniilgri]

@vanessayuenn
I have the same issue after upgrading the storybook to 7.4.0. Also tried clearing node_modules and clearing the npm cache.
It might not happen if you go from another story to the one where it is reproducible but when I refresh the page it is able to reproduce it.

[vanessayuenn]

@daniilgri do you have a reproduction repo you can share? If not, can you create one (see how to create a repro). We prioritize bug reports that have reproduction. Thank you! 🙏

[kasperpeulen]

cc @ndelangen

[larrygotto]

Same here.
I just found out that if you reload the page, go to another story and perform an action, the bug won't show up until you reload the page again.

[dylannnn]

Same issue here with version 7.4.1

[literalpie]

@jasosims I tried making a reproduction repo, but I'm not seeing this issue in a new project like your reproduction steps say.

I tried with Vite and Webpack, React 17 and 18.

[kasperpeulen]

@literalpie We can not reproduce this issue as well.

@dylannnn What happens if you remove your lock file and node_modules, does the error still appear?

[dylannnn]

Hi @kasperpeulen , after delete the node_modules folder and package-lock.json, run the npm install and start the storybook again, the issue is still present. Now the version is 7.4.2. Let me know if you need a stackblitz project to show you the setup.

[IanVS]

This looks like a duplicate of #23787. I've added some reproduction notes and a stackblitz there.