I updated the version: 3.7.0 and I get an unexpected error and it does not open

I get a similar message since updating:

TypeError: Cannot read property ‘getCollectionByRoute’ of undefined
at t.value (https://libermanlawfirm.com/wp-content/plugins/wordpress-seo-premium/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:145344)
at t.value (https://libermanlawfirm.com/wp-content/plugins/wordpress-seo-premium/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:144551)
at jc (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:134:123)
at gc (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:223)
at vb (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230)
at ub (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65)
at zd (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:124:449)
at ra (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:123:319)
at Object.enqueueSetState (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:189:231)
at r.q.setState (https://libermanlawfirm.com/wp-content/plugins/gutenberg/vendor/react.min.ab6b06d4.js:18:441)

Are you also using the Yoast SEO plugin?

There is a known issue with the latest version of Gutenberg and Yoast SEO that can cause this problem. Essentially, it is a minor mistake which can result in rather annoying consequences.

Yoast plans to have a fix out by Monday. You can find more information about this issue here:
https://github.com/Yoast/wordpress-seo/issues/10867#issuecomment-417696845
https://github.com/WordPress/gutenberg/issues/9506#issuecomment-417688790

In the meantime, they have a minor plugin fix there which can alleviate the issue, or you can revert to Gutenberg 3.6.2, which will also solve the problem until the Yoast plugin can be updated.