WeeklyRoundupBackgroundTask - no launch handler #18162
Merged
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.
This PR fixes an issue where iOS was throwing the following error NSInternalInconsistencyException: No launch handler registered for task with identifier org.wordpress.bgtask.weeklyroundup
This was caused by when FeatureFlag.weeklyRoundupBGProcessingTask was enabled the launch handler identifier registered changed. However WeeklyRoundupBackgroundTasks that were pre-scheduled the week before on existing app installs would be still scheduled with the old identifier.
Fixes #18156
To test:
Regression Notes
Potential unintended areas of impact
WeeklyRoundupNotificationTask
What I did to test those areas of impact (or what existing automated tests I relied on)
Tested on device
What automated tests I added (or what prevented me from doing so)
None
PR submission checklist:
RELEASE-NOTES.txt
if necessary.