Gutenberg is unable to open due to an unexpected error while ACF Pro is activated

[rpkoller]

Issue Overview

When creating an ACF Pro field group linking into a basic CPT "accordion" and then trying to open a post in the "posts" post type Gutenberg shows "The editor has encountered an unexpected error."

Steps to Reproduce (for bugs)

1. Install Gutenberg 1.9.0, ACF Pro 5.6.7 and CPT UI 1.5.6
2. Create a CPT "accordion" with CPT UI (simply set the title and the labels and deactivate the support for the editor and the image.
3. Create a field group in ACF Pro with one or two fields and set a rule to show these fields if the post type equals to the CPT "accordion"
4. Then go to the "posts" post type and try to edit the "Hello world!" post

Using:
WordPress 4.9.1
Gutenberg 1.9.0
ACF Pro 5.6.7
Custom Post Type UI 1.5.6

tested with Safari 11.0.2
WordPress installation is running on Local by Flywheel on OSX 10.11.6

Expected Behavior

Gutenberg opens the post

Current Behavior

instead I see the following:

• attempt recovery:

has no effect

• copy post text:

<p>Welcome to WordPress. This is your first post. Edit or delete it, then start writing!</p>

• copy error:

value@http://acfbasic.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513015316:21:14422
value@http://acfbasic.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513015316:21:14191
value@http://acfbasic.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513015316:21:13207
commitLifeCycles@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:37:430
c@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:16:127
k@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:19:412
Q@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:20:356
ed@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:24:365
updateContainer@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:197:397
http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:105:534
unbatchedUpdates@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:26:302
Bb@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:105:505
o@http://acfbasic.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513015316:11:52670
o@[native code]
value@http://acfbasic.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513015316:32:58655
value@[native code]
td@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:66:342
invokeGuardedCallback@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:117:354
invokeGuardedCallbackAndCatchFirstError@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:117:466
Bd@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:72:540
executeDispatchesInOrder@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:119:479
rd@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:65:84
forEach@[native code]
Ha@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:65:179
processEventQueue@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:125:136
handleTopLevel@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:130:73
hf@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:74:278
batchedUpdates@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:26:206
batchedUpdates@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:121:471
dispatchEvent@http://acfbasic.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.cc6ec027.js:123:273
dispatchEvent@[native code]

Possible Solution

Screenshots / Video

Related Issues and/or PRs

Todos

• Tests
• Documentation

[karmatosed]

Thanks for reporting this. Looks like the either the same error as already reported in #3934 or #3957 . I'll close this one for now but please if that fix doesn't solve your issue let us know. The fix will be in the next version of Gutenberg.

[rpkoller]

@karmatosed confirmed... 1.9.1 fixed the issue…