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

WakefulService is deprecated and needs to be replaced #147

Open
SCdF opened this issue Aug 14, 2019 · 2 comments
Open

WakefulService is deprecated and needs to be replaced #147

SCdF opened this issue Aug 14, 2019 · 2 comments
Labels
Priority: 1 - High Blocking the next release

Comments

@SCdF
Copy link
Contributor

SCdF commented Aug 14, 2019

See: https://github.com/commonsguy/cwac-wakeful

As of writing this says:

UPDATE 2019-05-11: Users of this library should migrate to JobIntentService or WorkManager from Android Jetpack. Those classes cover the primary WakefulIntentService use case, are officially supported, and help with the Android 8.0+ limitation on the life of background services. For the classic WakefulIntentService pattern of just overriding doWakefulWork(), migration to JobIntentService is a matter of changing the superclass, refactoring that method to onHandleWork(), and using enqueueWork() to start the work.

This library is officially discontinued, unless some use case arises where JobIntentService is unsuitable. If you think that you have one, file an issue here.

The rest of the documentation remains for the historical (and possibly hysterical) record.

This repository will be removed from public access on 1 December 2019.

It's unclear to me how severe that last line is, though I suppose it means that we won't have access to the source (unless we clone first) but builds will still continue to work (as they won't remove them from m2 or where-ever).

@garethbowen
Copy link
Member

It looks like WorkManager is the supported way forward. Be sure to include the GCM libraries to support API from 16 through 23, and the WorkManager library for 23+ (documentation).

@kennsippell
Copy link
Member

kennsippell commented Nov 5, 2020

This should be investigated as a potential blocker of Nepal project's upgrade to the latest gateway version. #135 (comment)

@kennsippell kennsippell added the Priority: 1 - High Blocking the next release label Nov 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: 1 - High Blocking the next release
Projects
No open projects
Development

No branches or pull requests

3 participants