Stats: Fix a crash in a remote service when accessing date formatter #22810
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.
Fixes #22796
Related PR: wordpress-mobile/WordPressKit-iOS#749
I couldn't reproduce the issue myself. Analysis of the stack trace suggests that the crash may have happened due to the date formatter being accessed from different threads and/or objects being deinitialized when being accessed. Although it's not 100% clear what exact changes in Stats made this issue happen. It could be triggered by some of the updates within
StatsPeriodStore
.More information here wordpress-mobile/WordPressKit-iOS#749
Testing
The changes are in
getData
method which is used when fetching chart information within Traffic or Day/Week/Month/Year Stats. They are only technical changes but the data for the chart should continue to be loaded.Regression Notes
None
Currently existing automated tests and manual testing
PR submission checklist:
RELEASE-NOTES.txt
if necessary.Testing checklist: