Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RuntimeException: PARAGRAPH span must start at paragraph boundary (973 follows .) #20792

Open
sentry-io bot opened this issue May 9, 2024 · 4 comments

Comments

@sentry-io
Copy link

sentry-io bot commented May 9, 2024

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)
@dangermattic
Copy link
Collaborator

dangermattic commented May 9, 2024

Thanks for reporting! 👍

@thomashorta
Copy link
Contributor

@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.

@geriux
Copy link
Member

geriux commented May 10, 2024

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?

@thomashorta
Copy link
Contributor

Good point! Sounds good to me! I'm marking it as Medium priority (since it's a crash but not affecting many people)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants