Implementation "androidx.work:work-gcm:$work_version"ĪndroidTestImplementation "androidx.work:work-testing:$work_version" Implementation "androidx.work:work-rxjava2:$work_version" Implementation "androidx.work:work-runtime-ktx:$work_version" Implementation "androidx.Português | العربية | 日本 | 한국어 | 简体中文 Livescribe™ 3 smartpen Implementation("androidx.work:work-runtime-ktx:$work_version") Implementation("androidx.work:work-runtime:$work_version") Implementation "androidx.work:work-multiprocess:$work_version" Implementation("androidx.work:work-rxjava2:$work_version") Let us know if you discover new issues or have Implementation("androidx.work:work-gcm:$work_version")ĪndroidTestImplementation("androidx.work:work-testing:$work_version")įor information on using Kotlin extensions, see the ktx documentation.įor more information about dependencies, see Add Build Dependencies. In this library before you create a new one. You can add your vote to an existing issue byįor more information. Version 2.9.0-alpha01 contains these commits. Precise scheduling of periodic workers via setNextScheduleTimeOverride.Instead of LiveData, Worker's progress now can be observed via Flow’s via WorkManager.getWorkInfosFlow and similar methods. This allows dynamic calculation of the next Periodic work schedule, which can be used to implement advanced features like adaptive refresh times, custom retry behavior, or making a newsfeed worker run before the user wakes up every morning without drift. WorkManager’s testing with threading matching should be used with these techniques to avoid cancelling a currently-running worker while scheduling the next one. Coroutines APIs such as CoroutineWorker have been moved from additional artifact work-runtime-ktx to the main artifact _EXECUTORS can be used to preserve executors set in Configuration and to use the real main thread.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |