[SOLVED] Use hardcoded versions instead > The ...
# refreshversions
m
[SOLVED] Use hardcoded versions instead
The AndroidX dependencies are annoying because they don’t follow a coherent versioning. @jmfayard
---- https://github.com/jmfayard/refreshVersions/issues/403 tl;dr: the 
lifecycle-extensions
 was not found (intended), because using version of 
2.3.0
 in a same group (
androidx.lifecycle
) tusing https://maven.google.com/web/#androidx.lifecycle:lifecycle-extensions:2.3.0 (not found, unless points to: 
2.2.0
) https://maven.google.com/web/#androidx.lifecycle:lifecycle-livedata:2.3.0 Is it possible to define different versions inside a same group? A suggestion for keyword to search(?), looks like I’m might missed this important samples/examples in the docs 🙏
l
@miqbaldc You need to stop using that lifecycle-extensions artifact, it's been deprecated and dropped since then.
m
Well noted, thanks for informing