Describe the bug
Its impossible to color Heading through heading block. So i need to use Classic block. But when i use Classic in columns it added correctly but when i refresh dashboard - Editor become unable to edit.
i've got "This block contains unexpected or invalid content." error message
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected to see Editor that i can edit as usual, and to to convert to html and edit as plain text
Screenshots
https://www.screencast.com/t/vcAL42Elccb
Desktop (please complete the following information):
Additional context
Wordpress 5.0
Thanks for reporting this issue! It's queued for testing, and in the mean time I thought you might want to check out this plugin which will let you add colors for headings: https://wordpress.org/plugins/advanced-rich-text-tools/
Thanks for the plugin. For now it can help me!
I tested adding a classic block inside of a column and was able to replicate the error described.
I followed the steps to reproduce listed by @AlexeySvidentsov
After which I get the following error:

I also encountered some further errors in testing that I don't believe would be an issue if the original problem is resolved.
I noticed that the error box has an option to convert the block back to the classic editor when clicking the toggle as shown below:

This works but changes the column widths in the editor only:

If you continue to refresh and edit it in this way, the editor removes the second column as well as any content in the column which is visible on the front end.

Tested in Chrome 70.0.3538.110 macOS Mojave 10.14.1
Still present with Gutenberg plugin v 5.0.0. Maybe the JS errors from the console help?
The validation of the block fails because there is content in the column.
I set up a new WordPress, no plugins besides Gutenberg, no themes besides Twentynineteen.
Same way of reproducing: Creating 2 columns, inserting a Classic Block, Saving, refresh/ switch to Code-Editor and back

Noting these related issues: #14323, #14025, #13187. Closing this as a duplicate, but keeping #13187 open as it has the most discussion around how to solve the issue