The issue with the update showed up in the block editor without an error — rather it conflicted with every other plug-in in use and turned every bit of the content in the editor — photos or text — invisible. There was no way to select the boxes or to see the content. The only part of the site which was unaffected was the background. lol lovely.
Sounds super weird. I hope the Gutenberg developers make a better system to help tell or show users when something goes wrong like this.
Perhaps it would be wise to post possible known conflicts in the notes when supplying the updates.
I think the point of the Gutenberg plugin is to test it out and find the bugs, as its not feasible for a developer to test it themselves on millions of different configurations. They have no idea what combination of plugins you are using.
Every few months the stable elements of the plugin are merged in to the core WordPress, so by that time, the bugs you experience (probably) don’t exist.
I think a better approach could be to rename or heavily warn users that using this Gutenberg plugin is probably going to break their site. And I will be suggesting this at the next developers meeting.
Upgrading plugins on a live site could always give you problems – this is not just a Gutenberg problem. If your host gives the options to have a staging site or development site, you should copy your site from live to staging to test the upgrades before doing on your live site. This way you can catch any issues, and not panic about your site being broken.
Glad you got it resolved anyway!