RichText/AztecWrapper crashes with "set span (x+1..x+1) ends beyond length x"

[daniloercoli]

I was able to reproduce the (in)famous set span (xx..XX) ends beyond... red screen error on Android, on both version 1.6.1, and 1.7.0 of gb-mobile.

There were some reports of this crash in Sentry, but we weren't aware fo steps to reproduce it.

I guess it's a mix of auto-corrector settings, and the Gboard keyabord, that can result into this problem. Cannot reproduce on AOSP keyboard.

v1.7 https://cloudup.com/c0tiPnG6sYn

• Start writing into a para block
• Make a typo on the last word
• Tap Enter, it does correct the word, and create a new line in the RichText field
• Tap enter again to create a new block
• New block is created, and the "extra" new line is then removed by our cleaning utils in the previous block
• Tap Backspace
• Boom

v1.6.1

• Start writing into a para block
• Make a typo on the last word
• Tap Enter, it does correct the word, and create a new line in the RichText field
• Tap Backspace (it does remove the autocorrection)
• Tap enter again to create a new block
• New block is created, and the "extra" new line is then removed by our cleaning utils in the previous block
• Tap Backspace
• Boom

Tested on Android 7.1, GBoard, on Nexus 5x

[marecar3]

Hey @daniloercoli I have tried to reproduce this one on Nexus 5x 8.1 but when I click on the enter, it creates a new block (not a new line). Is this specific to 7.1 Android?

[hypest]

👋 @marecar3 , reassigned this ticket to you since Danilo is going to divert effort to the "opt-in API" ticket instead.

[marecar3]

Thanks for the update! @hypest

[Tug]

Related to #872

[daniloercoli]

Closing this issue here, since testing steps provided are no longer replicating it.
We've already 2 other issues about the same crash in Aztec, and in GB-mobile (powered by Aztec), and will move those in GB-mobile v2 project.