Prevent crashes when retained posts are deleted - #26015
Open
crazytonyli wants to merge 2 commits into
Open
crazytonyli wants to merge 2 commits into
crazytonyli wants to merge 2 commits into
Conversation
Contributor
|
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 34454 | |
| Version | PR #26015 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | fad6452 | |
| Installation URL | 1hvhavh9bo048 |
Contributor
|
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 34454 | |
| Version | PR #26015 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | fad6452 | |
| Installation URL | 26o1cd6hplolg |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


The app may crash when delete/trash an post that's already deleted on the server but yet to be synced.
Here is the easiest way to reproduce the crash. It may not exactly match what's happening to the real users, but the root cause is the same:
Sentry records a new issue for this crash (i.e., https://a8c.sentry.io/issues/7703437016/?project=1438083), but it's not actually new (i.e., https://a8c.sentry.io/issues/7398708809/?project=1438083).