Fixed
Status Update
No update yet.
Comments
ju...@gmail.com
When you include androidx.lifecycle:lifecycle-runtime-ktx:2.2.0-alpha05, you are upgrading all of its transitive dependencies, which includes lifecycle-runtime. However, you are *not* upgrading lifecycle-process, which is still using the version of lifecycle from your lifecycle-extensions dependency (2.1.0).
You do any one of the following:
- Add an explicit dependency on lifecycle-process:2.2.0-alpha05 to pull in the new version that is compatible with lifecycle-runtime:2.2.0-alpha05
- Upgrade your lifecycle:extensions dependency to 2.2.0-alpha05 so that lifecycle-process is upgraded
- Remove the lifecycle:extensions dependency entirely and use only the lifecycle libraries you need (for example, use lifecycle-viewmodel-ktx if you want ViewModels) so that you don't pull in lifecycle-process at all
Mixing and matching Lifecycle versions is not a supported configuration, so I'd recommend keeping to using just a single version.
You do any one of the following:
- Add an explicit dependency on lifecycle-process:2.2.0-alpha05 to pull in the new version that is compatible with lifecycle-runtime:2.2.0-alpha05
- Upgrade your lifecycle:extensions dependency to 2.2.0-alpha05 so that lifecycle-process is upgraded
- Remove the lifecycle:extensions dependency entirely and use only the lifecycle libraries you need (for example, use lifecycle-viewmodel-ktx if you want ViewModels) so that you don't pull in lifecycle-process at all
Mixing and matching Lifecycle versions is not a supported configuration, so I'd recommend keeping to using just a single version.
ad...@google.com
ad...@google.com
Sorry and thank you for your time
ad...@google.com
After thinking about this some more, I think we can do something here to maintain compatibility since I suspect that there will be other cases where lifecycle-runtime is updated through some other dependency and that shouldn't force you to upgrade lifecycle-extensions / lifecycle-process.
Description
- Build Number: google/cheetah_beta/cheetah:14/AP11.231020.013.A1/11055090:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Google Assistant / Search
What steps would let us observe this issue?
1. I used the hot word to wake up the assistant but did not wake up.
What did you expect to happen?
Assistant to answer me.
What actually happened?
Nothing since I could not use it.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Extreme - device was unusable
Debugging information
Google Play services
com.google.android.gms
Version 234518038 (23.45.18 (190400-583159081))
System App (Updated)
Android System WebView
com.google.android.webview
Version 604506633 (119.0.6045.66)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.38-betterbug.external_20231004_RC05 (DOGFOOD)
To learn more about our feedback process, please visit