wordpress-mobile / wordpress-mobile/WordPress-Android
Migrate NotificationsProcessingService to WorkManager
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Android API 26 background service limitations were introduced. NotificationsProcessingService should either be migrated to WorkManager, or more likely, ViewModel. Background services may behave differently as updates are/were made.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating NotificationsProcessingService and reviewing how it handles background updates under the Android API 26 service limitations. Compare whether WorkManager or ViewModel fits the existing behavior, then define completion as a migration that preserves the required notification updates without relying on restricted background services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100