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.

Sign up for GitHub

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

Jump to bottom

Lifecycle methd warning #13006

Closed
dgwyer opened this issue Dec 19, 2018 · 2 comments
Closed

Lifecycle methd warning #13006

dgwyer opened this issue Dec 19, 2018 · 2 comments
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Bug An existing feature does not function as intended

Comments

@dgwyer
Copy link
Contributor

dgwyer commented Dec 19, 2018

Describe the bug
I'm seeing a lifecycle warning in the Gutenberg editor as follows:

Warning: Unsafe lifecycle methods were found within a strict-mode tree:
    in StrictMode
    in Unknown (created by r)
    in r (created by Context.Consumer)
    in WithSelect(Component)

componentWillUpdate: Please update the following components to use componentDidUpdate instead: t

To Reproduce

  1. Open Chrome dev tools with the console tab active.
  2. In WordPress admin click Pages > Add New to open up the Gutenberg editor.
  3. See error.

Screenshots
gb-error

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Chrome v70.0.3538.110
  • WordPress: 5.1-alpha-44295
  • Gutenberg Plugin: 4.7.1
  • Theme: Twenty Nineteen v1.0

Additional context

  • The only active plugin running is Gutenberg v4.7.1.
@designsimply designsimply added [Type] Bug An existing feature does not function as intended Framework Issues related to broader framework topics, especially as it relates to javascript [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed labels Dec 19, 2018
@designsimply
Copy link
Member

Thank you for reporting this! Closing as a duplicate of #7897 and noting that the remaining deprecated APIs surfaced by StrictMode of React 16.6 are being tracked at #11360.

@dgwyer
Copy link
Contributor Author

dgwyer commented Dec 20, 2018

Thanks, I'll watch those tickets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Bug An existing feature does not function as intended
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@designsimply @dgwyer