RuntimeException: PARAGRAPH span must start at paragraph boundary (973 follows .)
Sentry Issue: WORDPRESS-ANDROID-2Y9C
RuntimeException: Failure delivering result ResultInfo{who=null, request=2700, result=-1, data=Intent { (has extras) }} to activity {org.wordpress.android/org.wordpress.android.ui.posts.EditPostActivity}: java.lang.RuntimeException: PARAGRAPH span must start at paragraph boundary (973 follows .)
at android.app.ActivityThread.deliverResults(ActivityThread.java:5898)
at android.app.ActivityThread.handleSendResult(ActivityThread.java:5937)
at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:67)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:144)
...
(9 additional frame(s) were not displayed)
RuntimeException: PARAGRAPH span must start at paragraph boundary (973 follows .)
at org.wordpress.android.editor.AztecEditorFragment.onActivityResult(AztecEditorFragment.java:1885)
at org.wordpress.android.ui.posts.EditPostActivity.handleMediaSettings(EditPostActivity.kt:2881)
editorFragment?.onActivityResult(
at org.wordpress.android.ui.posts.EditPostActivity.handleRequest(EditPostActivity.kt:2844)
RequestCodes.MEDIA_SETTINGS -> handleMediaSettings(data)
at org.wordpress.android.ui.posts.EditPostActivity.onActivityResult(EditPostActivity.kt:2802)
handleRequest(requestCode, data)
...
(18 additional frame(s) were not displayed)
Thanks for reporting! 👍
@geriux I see you worked on Aztec lately so you probably have a better understanding of how it works or if any recent changes could have caused this, is it OK if I assign it to you?
The crash was first seen recently on 24.7, so it might be something new.
I searched for that error on Sentry since usually it just creates new events and I see events back to 24.3.1 so it's not a recent regression. Maybe we could add this to the maintenance board, what do you think?
Good point! Sounds good to me! I'm marking it as Medium priority (since it's a crash but not affecting many people)