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