Have an m3 dependency issue I m currently using ```androidx

Question

Have an m3 dependency issue I m currently using ```androidx compose material3 material3 1 1 0 alpha04``` with no issues If I update to alpha05 I start getting compile time issues related to my lifecycle lib imports ```import androidx lifecycle Transformations``` error `Unresolved reference Transformations` Any folks from m3 team might now if there were some transitive dependencies that changed or something from alpha 4 to 5

Ian Lake · Answer

Did you try the <https developer android com jetpack androidx releases lifecycle 2 6 0 alpha05|Lifecycle release notes> They specifically call out the Transformations change in Lifecycle you should have always been using the Kotlin extension syntax for Transformations in your Kotlin code

Colton Idle · Answer

see no evil

Colton Idle · Answer

I am ashamed because I typically read the release notes and diffs and somehow while debugging this I went and checked and I still missed it Maybe I looked at the wrong dep Thanks < Ian Lake>

Marcin Wisniowski · Answer

Aren t you the guy who posts these great release note compilations smile

Ian Lake · Answer

Ha I post about non Compose release notes I even called out this specific change when it came out and

Colton Idle · Answer

This was in lifecycle I only post for compose but yes I also checked lifecycle I must ve just been tired last night

Colton Idle · Answer

And I follow Ian sob

Colton Idle · Answer

I m going to sleep lol

Marcin Wisniowski · Answer

Haha sorry I meant Colton <https kotlinlang slack com archives CJLTWPH7S p1677112006723889> But applies to you Ian too clearly

Ian Lake · Answer

Yeah Colton s release notes specifically for this channel are really good too +1 +1

francisco · Answer

I haven t used mastodon but quick question Do i need to be invited join the `androiddev` mastodon server to follow you

Ian Lake · Answer

No you can follow anyone from any server no matter what server you are on

Andy Himberger · Answer

I think the compose release notes never called out that they updated their dependencies to activity 1 7 core 1 9 and lifecycle 2 6 in 1 4 beta01 before that the release notes did say when they updated to lifecycle 2 5 x I try to do upgrades individually when I can in case we need to rollback it doesn t have to rollback everything added some speedbumps into our 1 4 adoption timeline