Background location tracking issues on Samsung devices running Android 14

[argenkiwi]

What does it have to do with Molecule you ask? Well, I was using molecule to wrap my location requests in a disposable effect in a foreground service so I could re-issue the request when one of the keys of the effect changed and also remove the request when the service was done. There is no good reason for anyone to do this, I just thought it looked nice and clear in the code and it seemed to be working fine... until Samsung released their distribution of Android 14. What I began experiencing was that when the app was in the background, the location updates stopped and then resumed afterwards. This was not happening on a Pixel 5 running Android 14 or on Samsung devices running Android 13 and below. I spent sometime making a project that just did tracking to isolate all the variables and I realized that by not using molecule the problem was gone. But why?

I'll attempt to put together a minimal example project later this week in case anyone wants to have a look. I just had to share it because it caused me pain I don't wish any other fellow dev.

[argenkiwi]

To add another clue to the riddle, it seems the problem is not using molecule in the service but using DisposableEffect with it, and for some reason this became a problem on Samsung's One UI 6.x only.