Redoing insertion of an image loses subsequent redo history

[mchowning]

Describe the bug
When using redo to restore an image in an image block, the subsequent redo history is lost. In other words, any of the changes done after the image was inserted cannot be restored.

To Reproduce
Steps to reproduce the behavior:

1. Insert an image block
2. Add an image to the image block
3. Add some text to the post (could be in the caption or in a new block)
4. Tap undo until the image block is empty (i.e., it has the "ADD IMAGE" text)
5. Tap redo to restore the image to the image block
6. Observe that the redo button is now disabled and you cannot restore any of the changes you made after adding the image

Expected behavior
It should be possible to restore changes made after restoring the image inserted into an image block.

Screenshots

Smartphone (please complete the following information):

• Device: Pixel 1, iPhone Xr
• OS: e.g. iOS 13.5.1, Android X
• Version: WPAndroid 15.2.1, WPiOS Internal 15.3.0.202007137417bf8

Additional context
Although there is probably a different underlying cause, there is an iOS specific issue whereby links that open new tabs also lose undo history: #2091

[guarani]

I tried reproducing and this is what I found:

• WordPress app 15.4 beta for Android on physical device: Reproduced
• WordPress app 15.4 beta for iOS on physical device: Reproduced
• Current Gutenberg mobile demo apps for Android on physical device: Could not reproduce
• Current Gutenberg mobile demo apps for iOS: Could not reproduce
• On Android, it's reproducible with both the Google Gboard and Samsung keyboard
• This is looking to be a different issue to [iOS] Redo history lost after adding link to text #2091, which seems to be remedied by adding the missing rel attribute here — that fix seems specific to format types, while this issue doesn't have to do with format types

[AmandaRiu]

FYI: Still an issue as of 1.57.0. Tested on a physical Pixel 4 running Android 11 w/ Gboard:

screencapture-1626125609561.mp4

[guarani]

I'm no longer seeing this issue on WPiOS 18.1 (18.1.0.4). I am still seeing the issue occasionally on WPAndroid 18.2-rc-3 (2 out of 4 attempts).