Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: received updateGlobals but was unable to determine the source of the event, received updateGlobals but was unable to determine the source of the event #15659

Closed
ChaitanyaKrishnaPappala opened this issue Jul 22, 2021 · 17 comments

Comments

@ChaitanyaKrishnaPappala

Describe the bug
When I try to build and serve the build version of storybook this issue arises.

To Reproduce
Run

  1. build-storybook -c .storybook -o .storybook-static
  2. npx serve -s .storybook-static

System
Mac OS
Dependencies:

  "react": "^16.13.1",
 "@storybook/addon-actions": "^6.1.20",
 "@storybook/addon-essentials": "^6.1.20",
 "@storybook/addon-knobs": "^6.1.20",
 "@storybook/addon-links": "^6.1.20",
 "@storybook/node-logger": "^6.1.20",
 "@storybook/preset-create-react-app": "^3.1.6",
 "@storybook/react": "^6.2.9"

Below is my .storybook/main.js file

module.exports = {
  stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/preset-create-react-app',
  ],
};

Additional context
Throws the following errors in the console,

  1. received sharedStateChanged-manager-storybook/viewport but was unable to determine the source of the event
  2. received updateGlobals but was unable to determine the source of the event

Screen Shot 2021-07-22 at 2 40 06 PM

@Jordan-Eckowitz
Copy link

Yeah seeing the same issue when I deploy Storybook. When I run it locally using serve it works fine. Could this be a CORS issue? Perhaps something related to this: #11892

@shilman
Copy link
Member

shilman commented Jul 29, 2021

Do you a have a reproduction repo you can share? If not, can you create one? See how to create a repro. We prioritize issues with reproductions over those without. Thank you! 🙏

@shilman shilman added the core label Jul 29, 2021
@lorcannn
Copy link

I had the same problem when i am run:

  1. npm run build-storybook
  2. serve -s storybook-static

image

🥳🥳The finally I resolve this problem when i am run:
serve storybook-static

@Jordan-Eckowitz
Copy link

@shilman I think you can close this ticket - was an AWS problem addressed in this closed issue: #12538 (comment)

@shilman shilman closed this as completed Dec 28, 2021
@mduenias
Copy link

FYI I am getting this error when using this recipe: https://github.com/storybookjs/storybook/blob/next/addons/docs/docs/recipes.md#reordering-docs-tab-first

export const parameters = {
  previewTabs: { 'storybook/docs/panel': { index: -1 } },
}

Both when running storybook locally and with the static build.
I would love to have a way to reorder the tabs without causing this warnings.

@designmatty
Copy link

I'm unfortunately seeing the same as @mduenias. For now, I'm just going to remove the reordering logic until it's fixed.

@somenickname
Copy link

@mduenias @designmatty could you check that changes in previewTabs also trigger double bundle loading?

@HyperLife1119
Copy link

HyperLife1119 commented Jul 12, 2022

FYI I am getting this error when using this recipe: https://github.com/storybookjs/storybook/blob/next/addons/docs/docs/recipes.md#reordering-docs-tab-first

export const parameters = {
  previewTabs: { 'storybook/docs/panel': { index: -1 } },
}

Both when running storybook locally and with the static build. I would love to have a way to reorder the tabs without causing this warnings.

Same problem, still exists in Storybook 6.5.9. Does this issue need to be reopened? @shilman

image

@vhoyer
Copy link

vhoyer commented Jul 12, 2022

I think we should open another issue exclusively for this reordering error

@usrrname
Copy link
Contributor

usrrname commented Oct 6, 2022

Seems this still exists!

@mogamogua
Copy link

it still exists 🥲

@AlexeyTeterin
Copy link

Still same issue on v 7.6.10

@JuhG
Copy link

JuhG commented Apr 30, 2024

We have the same issue on 8.0.5.
Created a discussion that's basically the same issue: #26941

After some digging, this seems to be the issue:

this.config.page === 'preview' ? rawEvent.origin : getEventSourceUrl(rawEvent);

When getEventSourceUrl is called, event.source is undefined, but - in our case - only sometimes. So maybe some race condition?

@shilman can we reopen this?

@shilman shilman reopened this Apr 30, 2024
@shilman shilman moved this to Empathy Backlog in Core Team Projects May 25, 2024
Copy link
Contributor

Hi there! Thank you for opening this issue, but it has been marked as stale because we need more information to move forward. Could you please provide us with the requested reproduction or additional information that could help us better understand the problem? We'd love to resolve this issue, but we can't do it without your help!

@github-actions github-actions bot added the Stale label Jun 16, 2024
Copy link
Contributor

I'm afraid we need to close this issue for now, since we can't take any action without the requested reproduction or additional information. But please don't hesitate to open a new issue if the problem persists – we're always happy to help. Thanks so much for your understanding.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
@github-project-automation github-project-automation bot moved this from Empathy Backlog to Done in Core Team Projects Jun 26, 2024
@MustafaLeanTech
Copy link

Also having the same issue on storybook v8.2.1

@JuhG
Copy link

JuhG commented Aug 2, 2024

There's now a reproduction repo in the related discussion: #26941 (comment)

It shows that it doesn't show the error on simple story pages, but produces it on more complicated pages 100% of time - while using the exact same components, just rendering the same thing multiple times. So - as @nukemonk points out - it does seem like a race condition.

Repo: https://github.com/nukemonk/globals_toolbar_error
Chromatic: https://66ac97cfb6985b19d709445f-szcqjhqcuf.chromatic.com/?path=/docs/example-button-with-problem--docs

Screenshot 2024-08-02 at 10 49 51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests