Carlos Garcia

As far as I investigated, the issue seems related to the block processors executed for each media associated to the post when saving ([reference 1](https://github.com/wordpress-mobile/WordPress-iOS/blob/e29a8edf6f2cdef7915e7cb5b924c8251763799d/WordPress/Classes/Services/PostCoordinator.swift#L158), [reference 2](https://github.com/wordpress-mobile/WordPress-iOS/blob/e29a8edf6f2cdef7915e7cb5b924c8251763799d/WordPress/Classes/Services/PostCoordinator.swift#L328-L409)). I haven't narrowed...

## Block processing benchmark I benchmarked the function [`updateReferences`](https://github.com/wordpress-mobile/WordPress-iOS/blob/80835e2b49ff6dd5145f66c214a6053129b3f582/WordPress/Classes/Services/PostCoordinator.swift#L375-L456) that is invoked before saving the post ([reference](https://github.com/wordpress-mobile/WordPress-iOS/blob/80835e2b49ff6dd5145f66c214a6053129b3f582/WordPress/Classes/Services/PostCoordinator.swift#L202-L205)). This function is the one that uses the block processors to ensure that...

Hey @notandyvee 👋 , the process to update the target SDK will be similar to the one documented in https://github.com/wordpress-mobile/gutenberg-mobile/issues/5556. The main difference is that in this case, we'll need...

@notandyvee I couldn't find a branch in [WordPress-Android](https://github.com/wordpress-mobile/WordPress-Android) related to the target SDK upgrade. I'd like to test the React Native patch to address the error `java.lang.RuntimeException: Requested enabled DevSupportManager,...

@notandyvee I have prepared the different PRs needed for this tracking issue. The only one remaining is updating the Aztec version, however, we'd first need to tackle https://github.com/wordpress-mobile/AztecEditor-Android/issues/1072. Let me...

> > The only one remaining is updating the Aztec version, however, we'd first need to tackle [wordpress-mobile/AztecEditor-Android#1072](https://github.com/wordpress-mobile/AztecEditor-Android/issues/1072). > > I can attempt to tackle that. How are gutenberg and...

This issue still happens after [this fix](https://github.com/WordPress/gutenberg/pull/54382) was released in version `23.4`. However, seems that the stack trace points to a different origin: ``` packages/react-native-editor/src/jsdom-patches.js:45:Node.prototype.contains packages/react-native-editor/src/jsdom-patches.js:46:Array.prototype.some.call$argument_1 packages/react-native-editor/src/jsdom-patches.js:45:Node.prototype.contains packages/react-native-editor/src/jsdom-patches.js:46:Array.prototype.some.call$argument_1 packages/react-native-editor/src/jsdom-patches.js:45:Node.prototype.contains packages/react-native-editor/src/jsdom-patches.js:46:Array.prototype.some.call$argument_1...

Fixed in https://github.com/WordPress/gutenberg/pull/55613.

Re-opening this issue as we received a new crash in version `23.8` (`23.8.0.3`). So far, we only received one event so it's likely that the reproducibility is lower than the...

Seems we have another instance of this issue but reported in a different Sentry event (https://github.com/wordpress-mobile/gutenberg-mobile/issues/6411#issuecomment-1867882684): **Symbolicated stack trace:** ``` gutenberg/packages/blocks/src/api/raw-handling/utils.js:129:deepFilterNodeList gutenberg/packages/blocks/src/api/raw-handling/utils.js:130:Array.from.forEach$argument_0 gutenberg/packages/blocks/src/api/raw-handling/utils.js:129:deepFilterNodeList gutenberg/packages/blocks/src/api/raw-handling/utils.js:130:Array.from.forEach$argument_0 gutenberg/packages/blocks/src/api/raw-handling/utils.js:129:deepFilterNodeList gutenberg/packages/blocks/src/api/raw-handling/utils.js:130:Array.from.forEach$argument_0 gutenberg/packages/blocks/src/api/raw-handling/utils.js:129:deepFilterNodeList gutenberg/packages/blocks/src/api/raw-handling/utils.js:130:Array.from.forEach$argument_0 gutenberg/packages/blocks/src/api/raw-handling/utils.js:129:deepFilterNodeList gutenberg/packages/blocks/src/api/raw-handling/utils.js:130:Array.from.forEach$argument_0...