Make it easier to react to Lifecycle State changes in Compose [235529345]

Fixed

Feature Request

Status Update

No update yet.

Description

il...@google.com

created issue #1

Jun 9, 2022 11:56PM

Component used: Lifecycle

Version used: 2.5.0-rc01

Reacting to a Lifecycle.State changes is currently fairly complicated in a Jetpack Compose based app, requiring a DisposableEffect based approach with registering a LifecycleObserver with the LocalLifecycleOwner.

Ideally, this would come in two forms:

I'd like to see a way to capture the current Lifecycle.State as State, perhaps something like LocalLifecycleOwner.current.lifecycle.currentStateFlow.collectAsState()
I'd like a way to run side effects when the Lifecycle changes, perhaps using a custom LifecycleEventEffect that would only run the effect when the Lifecycle.State changes.

Comments

il...@google.com <il...@google.com> Sep 13, 2022 12:14AM

Assigned to sa...@google.com.

tr...@gmail.com <tr...@gmail.com> #2Oct 26, 2022 07:14AM

Information redacted by Android Beta Feedback.

a....@gmail.com <a....@gmail.com> #3Nov 4, 2022 10:30PM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

sj...@gmail.com <sj...@gmail.com> #4Feb 23, 2023 07:56AM

The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(https://developer.android.com/preview/release-notes.html).

sj...@gmail.com <sj...@gmail.com> #5Mar 7, 2023 11:30AM

How long till this hit stable?

The issue is really annoying. Pixel 8 Pro + Pixel Buds A-Series + Pixel Watch. This should work without any issue and instead we have to manually disable Bluetooth on the watch whenever we use the buds. Don't you have quality controls on your products interactions?

sa...@google.com <sa...@google.com> Mar 14, 2023 08:18PM

Accepted by sa...@google.com.

ap...@google.com <ap...@google.com> #6Mar 16, 2023 07:03PM

Have the same issue. Pixel buds disconnect constantly. Works without issue on Pixel 6 with Pixel Watch.

-Pixel 8, Pixel Buds A, Pixel Watch-

[Deleted User] <[Deleted User]> #7Mar 22, 2023 05:51PM

I have the same issue. Pixel Buds A, Pixel Watch, and Pixel 8 Pro. If I turn off my Pixel Watch my buds no longer disconnect.

[Deleted User] <[Deleted User]> #8Mar 22, 2023 05:51PM

Same issue. Upgraded to Pixel 8 Pro and did not have similar issue with older Pixel 4. Poor service from Google

[Deleted User] <[Deleted User]> #9Mar 22, 2023 05:51PM

Yep both of my pair of buds are doing the same on my pixel 6 pro while google watch is connected I have my watch on aeroplane mode to stop it but shorely that can't be the only answer.

ap...@google.com <ap...@google.com> #10May 2, 2023 10:39PM

We have been waiting for a fix since October 2023. But this is still not fixed in the March update!

ap...@google.com <ap...@google.com> #11May 4, 2023 10:09PM

Any updates here? This is infuriating

ap...@google.com <ap...@google.com> #12May 4, 2023 10:09PM

Google, Status-Update?!

st...@gmail.com <st...@gmail.com> #13May 29, 2023 02:24PM

Same issue here. Pixel 8 Pro + Buds A + Watch. Buds either constantly disconnecting or nor playing audio while connected after some time (usually around 5 to 10 minutes). Buds worked flawlessly with Pixel 6a and same Watch. Would appreciate to get some information when this will be fixed. Cannot use Buds with my brand new 1000+ Pixel 8 Pro and my Pixel Watch. That's really a shame.

il...@google.com <il...@google.com> #14May 30, 2023 10:58PM

#13
This should have been fixed for QPR2 and Pixel Buds A

ap...@google.com <ap...@google.com> #15Jun 1, 2023 11:36PM

The issue is still there. Its really annoying to have the buds disconnected while on a call. I am using a buds a series and a 6-pro. Really really really frustrated.

sa...@google.com <sa...@google.com> Jun 21, 2023 07:39PM

Marked as fixed.

[Deleted User] <[Deleted User]> #16Jun 22, 2023 04:31AM

Just a feedback for Google.

The bug was reported on the 26th of December 2023. It was fixed on the 5th of January 2024 (comment #4), very fast considering the Xmas holidays in the middle.

What is inaccettabile is that the fix, hasn't been released to devices after 6 months. It is still in the Android 15 beta.

This is a but affecting 2 of your flagship products. You need to have some way to expedite the release of this kind of thing.

It should have been released in Android 14 as an hotfix in January.

Please fix your process.

ka...@gmail.com <ka...@gmail.com> #17Jul 7, 2023 08:12AM

Yeah ive been putting up with it, but I'm not going to buy google hardware again. I'm thinking of detatching from google entirely. I've lost my trust in them.

na...@google.com <na...@google.com> #18Jul 26, 2023 05:21PM

Also been impacted by this and had the buds replaced by Google originally. This is brand damaging and must be costing a fortune as well - surprised they've let this bug get so far..

sj...@gmail.com <sj...@gmail.com> #19Jan 11, 2024 06:40AM

still having this problem. All firmware updated. Pixel7

ey...@gmail.com <ey...@gmail.com> #20Jan 11, 2024 02:10PM

comment#19

,

Even though the issue sounds similar, the internal root cause would be different, so please raise a separate ticket along with the bugreport from your device.

Thanks.

jb...@google.com <jb...@google.com> #21Jan 11, 2024 02:20PM

Yes, those are the Lifecycle.States that reflect those particular Lifecycle.Events. Please take a look at the Lifecycle guidance for more details.

ey...@gmail.com <ey...@gmail.com> #22Jan 11, 2024 03:21PM

Sorry, my bad, didn't realize that. But since this is a flow, shouldn't it emit events rather than states? What is the usecase to react to two states that never become invalid? The docs claim this is in order to "read changes in the lifecycle" but it would require further processing to be able to realize what's going on.

jb...@google.com <jb...@google.com> #23Jan 11, 2024 04:32PM

Receiving a state from the flow would be the signal that a change has occurred and the new state is that particular change. There are cases where you don't care how you get to a state, just that you are there. We also offer LifecycleEffects to assist with use cases for Lifecycle.Events.

il...@google.com <il...@google.com> #24Jan 11, 2024 05:31PM

If you look at the release notes, you'll find two separate sections - one on Lifecycle Events (where you can use Lifecycle.asFlow() to get a Flow of Lifecycle.Event) and one for Lifecycle State (where you can use Lifecycle.currentStateFlow to get the current Lifecycle.State).

Make sure you are using the right API.

ey...@gmail.com <ey...@gmail.com> #25Jan 12, 2024 09:20AM

Thank you both for all the guidance. I guess my issue is that I'm trying to use it outside of Compose, to replace a simple lifecycle event observer, since it just feels like a nicer interface to collect a flow. For Compose, the effects work fine, indeed.

il...@google.com <il...@google.com> #26Jan 16, 2024 08:25PM

Lifecycle.asFlow() works outside of Compose too and gives you Lifecycle.Event instances as they occur. That's why that API exists separately from currentStateFlow.