IssueTracker

I have read that WorkManager 2.7.0 is needed if an app targets API 31/Android 12, and in order to do that, I have added setExpedited(OutOfQuotaPolicy.RUN_AS_NON_EXPEDITED_WORK_REQUEST) to my OneTimeWorkRequestBuilder and added the necessary changes in the AndroidManifest as well. Now running my app I've encountered the following error:

java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a ListenableWorker to provide an implementation for `getForegroundInfoAsync()`

So I tried looking up info on how to do implement this, and found no examples available from official Google sources (Github, developers.android.com, changelog, etc), but found this

answer over in Stackoverflow, but it is for Coroutines.

My question is how do you implement the said getForegroundInfoAsync for RxWorker when getForegroundInfoAsync has to return ListenableFuture<ForegroundInfo>--reading the docs it seems I have to add Guava to my app to do this? Since the docs for ListenableFuture says to Avoid implementing ListenableFuture from scratch. If you can't get by with the standard implementations, prefer to derive a new Future instance with the methods in Futures or, if necessary, to extend AbstractFuture.

I also have tried adding a SettableFuture but it is annotated with @RestrictTo(RestrictTo.Scope.LIBRARY_GROUP)

Nvm, I just annotated my implementation of getForegroundInfoAsync with @SuppressLint("RestrictedApi") and created a SettableFuture. It seems to work well.

You're right, we should add Rx support for this method.

In meanwhile, you can use CallbackToFutureAdapter instead of restricted API. It is safer that SettableFuture and allows you avoid dependency on restricted APIs.

Thanks for showing that callback. Honestly this whole getForegroundInfoAsync is still unclear to me--since I'm using RxWorker, I usually create a notification inside createWork and when the work is ongoing, I display a notification with progress bar via doOnSubscribe, something like this:

    api.doSomeWork()
       .doOnSubscribe { 
           // display notification with progress bar
           setForegroundAsync(ForegroundInfo(notificationId, notificationBuilder.build()))
       }

So how getForegroundInfoAsync fits into this, I don't understand. The effect of implementing getForegroundInfoAsync is that I actually get two notifications, the one that displays a progress bar that's already full, and another one that's actually updated.

Edit: actually never mind, getForegroundInfoAsync has nothing to do with having two notifs. Just figured it out and getForegroundInfoAsync is called before createWork.

https://issuetracker.google.com/issues/157590191

Passing to Jose regarding release

Any update on the release date please?

I ma still waiting for the release. I have tried the SNAPSHOT version but that also requires androidCompileSdkVersion = 35, which is inconvenient with all the edge-to-edge changes. Is it possible to have the release and not require androidCompileSdkVersion 35?

Any updates? Will M3 be able to access NavGraphBuilder.bottomSheet on the next stable release? Regular material has this planned according to: https://issuetracker.google.com/issues/376169507

Type-safe support for the material-navigation artifact was shipped in 1.8.0-alpha01, so we will be marking this issue as fixed.

#14: Can you please create a new issue with a repro case? Thank you!

#15: At the current time, M3 support for material-navigation is not prioritized. M3 sheets are implemented through dialogs and are shown on top of other layouts regardless of the composable's position in the hierarchy. If you are looking to have sheet destinations on the back stack, we recommend implementing a custom Navigator. Please create a new issue asking for M3 support if this is an important use case for you.

#16: There is already a long standing issue: https://issuetracker.google.com/issues/328949006