Carlos Garcia

> ... > `facebook::react::JSIExecutor::handleMemoryPressure` > ... In the stack trace, there's a call to a function that references memory pressure. Following https://github.com/wordpress-mobile/WordPress-Android/issues/19516#issuecomment-179838258, the theory about low memory issues in low-end...

PR ready 😉

> @geriux @fluiddot any idea why the mobile tests are failing here? The error seems similar to the one described [here](https://github.com/WordPress/gutenberg/pull/59005#issuecomment-1943677059). We solved it by adding the mobile native version...

Thanks @iamacup, I’ll take a look to your fork (nice work btw).

This issue looks similar to https://github.com/wordpress-mobile/WordPress-FluxC-Android/issues/1579 but affecting a different parameter. I wonder if it could be addressed following the same approach as applied in https://github.com/wordpress-mobile/WordPress-FluxC-Android/pull/2389. This implies storing the...

> The blocks that I maintain here look fine: Bauhaus Centenary, Event, Model Viewer, Starscape, and Waves. > It looks like the waves and book blocks are a bit broken,...

Following https://github.com/Automattic/block-experiments/pull/340#pullrequestreview-1794216776, I tried to address the issue when running tests but seems more complex than I originally thought. In the newer version of `@wordpress/scripts`, the Jest version is updated...

Probably related to https://github.com/WordPress/gutenberg/issues/55652.

This issue is impacting around 0.01% of users in version `22.5.1.0`. Marking it with a `Medium` priority as it's a crash with low impact.

There's a known case on Atomic sites where UBE results in the error `Unable to load the block editor right now`: [Editing unsupported blocks is disallowed on Classic-enabled Atomic sites](https://github.com/wordpress-mobile/test-cases/blob/trunk/test-cases/gutenberg/unsupported-block-editing.md#editing-unsupported-blocks-is-disallowed-on-classic-enabled-atomic-sites)....