Describe the bug
I Updated to v3.3.0 because I wanted to re-test a previous issue. When I tried to edit the page, the main content area was blank. The only items that showed on the page were the left-hand menu and top admin bar.

When viewing the console, the following errors were listed:

I tried disabling ACF (and another ACF addon) but the editor still wouldn't display, so it's obviously not an error caused by ACF.
To Reproduce
Steps to reproduce the behavior:
_macOS Sierra 10.12.6 (16G1408)
Firefox Quantum 61.0.1 (64-bit)
Gutenberg 3.3.0_
Yes, same here...
index.js:37 Uncaught TypeError: Cannot read property 'keycodes' of undefined
at Object.
at n (index.js:1)
at index.js:1
at index.js:1
(anonymous) @ index.js:37
n @ index.js:1
(anonymous) @ index.js:1
(anonymous) @ index.js:1
post-new.php:184 Uncaught TypeError: wp.blocks.unstable__bootstrapServerSideBlockDefinitions is not a function
at post-new.php:184
(anonymous) @ post-new.php:184
index.js:1 Uncaught TypeError: Cannot read property 'withSafeTimeout' of undefined
at Object.316 (index.js:1)
at e (index.js:1)
at wp.nux.0 (index.js:1)
at index.js:1
316 @ index.js:1
e @ index.js:1
wp.nux.0 @ index.js:1
(anonymous) @ index.js:1
index.js:12 Uncaught TypeError: Cannot read property 'withFilters' of undefined
at Object.
at n (index.js:1)
at index.js:1
at index.js:1
(anonymous) @ index.js:12
n @ index.js:1
(anonymous) @ index.js:1
(anonymous) @ index.js:1
index.js:12 Uncaught TypeError: Cannot read property 'withFallbackStyles' of undefined
at Object.
at n (index.js:1)
at index.js:1
at index.js:1
(anonymous) @ index.js:12
n @ index.js:1
(anonymous) @ index.js:1
(anonymous) @ index.js:1
index.js:12 Uncaught TypeError: Cannot read property 'withState' of undefined
at Object.
at n (index.js:1)
at index.js:1
at index.js:1
(anonymous) @ index.js:12
n @ index.js:1
(anonymous) @ index.js:1
(anonymous) @ index.js:1
post-new.php:1880 Uncaught TypeError: Cannot read property 'initializeEditor' of undefined
at HTMLDocument.
(anonymous) @ post-new.php:1880
@maddisondesigns seems that an simple delete of cache + reload with CTRL+F5 fixes this. At least for me it its working now after this steps.
Same here in a specific site in a multisite with subdomain install. WP 4.9.7 and Gutenberg 3.3.0. The console shows the same messages mentioned by @thebugfixnet and they persist after cleaning all caches (server and browser, storage API, etc) and forcing reload.
@thebugfixnet Yep, that worked for me as well. Thanks for that.
@maddisondesigns are you using a multisite with subdomain install?
@designsimply Nope, mine was just a local site on my own development server. It's a copy of my main business site which is just a regular 'ol WordPress single site install.
Clearing the (browser) cache seemed to fix my issue but it looks like @celsobessa is still having the same issue on his multisite.
I hope we're not going to be seeing these issues once this is in core.
@celsobessa could we move to the forums to do further troubleshooting? It would be helpful to work through the details for your specific case there to come up with some reliable steps to reproduce the bug before adding details back here on GitHub. https://wordpress.org/support/plugin/gutenberg/
Would it be possible to include the following details in the forums?
Most helpful comment
@thebugfixnet Yep, that worked for me as well. Thanks for that.