❗Heads-up❗: Make sure you declare the ksp plugin in root gradle but apply in app gradle. If you don't declare it in root, you'll run into gradle issues.
can you help? I just can't get it to run. I am using Android Studio Hedgehog. How do I "eclare the ksp plugin in root gradle but apply in app gradle"...thanks!
I love the workings you have provided, I followed the steps to migrate ksp for room/dagger successfully. Thanks for always keeping us ahead in the Android Game.
Thanks. Just few weeks ago I tried KSP but it seems it has problems with Dagger Hilt. There was warning saying something was not recognized. I'm glad that latest Dagger Hilt supports KSP.
@Philipp let's say you want to keep databinding or something that doesn't support KSP yet, if we use Kapt for those and KSP for Room and Hilt, do we get some improvements in build times? or we only get faster builds if we give up on Kapt entirely?
complete ksp is faster as compiler don't have to wait for java stubs generation. if you use both then you won't get any significant changes to build time.
you did good , the only downside is that the version for the hilt compiler and plugin is now 2.50 and the need of jvm in the project gradle file for it to work
how can we use KSP and Navigation component together? I get that error below; Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
4:34 I hope the ai tool will help with this versioning and confusing configuration details some day soon It’s a complete nightmare on android and needs to be addressed It’s the most annoying thing on android!
Do you have any issues with hilt testing? I'm getting lots of error. I guess since this is the first supported version there are many issues with testing.
Hey phillip, So I am using kotlin compiler version 1.9.10 and everything with KSP and other dependencies are set but when I try to implement Hilt dependencies just the ones you used here Im met with error "Unsupported class file major version 63"... Im using Hilt version 2.48.1
this is did not work in my project. I had a problem with ksp failed in room to find some types of the properties. I think it is because i use classes generated by GraphQL Apollo library.
Unfortunately if you use ksp with kapt e.g if you're using libraries that don't yet support ksp, then you'll still have slower build times and ksp will be useless at that time
KSP still isn't useless - the more tools you have on KSP instead of KAPT the better state your build is in. However, it's true that you'll get the greatest improvement if you completely remove KAPT. What libraries do you have that still need KAPT?
@@ChrisAthanas sorry guys but it's 101 of optimalization to measure before and after optimalizations are applied :D thumbnail is flashy and says that builds are up to 2 times faster, yet 0 proof or real observation is presented, therefore it is lying/misleading, not backing up serious claims. Do that to a client and you'll make yourself look like a dummy.
❗Heads-up❗:
Make sure you declare the ksp plugin in root gradle but apply in app gradle.
If you don't declare it in root, you'll run into gradle issues.
True, I had issues but when I moved it project module it worked fine
can you help? I just can't get it to run. I am using Android Studio Hedgehog. How do I "eclare the ksp plugin in root gradle but apply in app gradle"...thanks!
Yeeey! Finally KSP is supported by Dagger-Hitl! 🥳
Yep, dagger-hilt 2.47 was what made me stick with kapt
I love the workings you have provided, I followed the steps to migrate ksp for room/dagger successfully. Thanks for always keeping us ahead in the Android Game.
The source to check the compatible version of Kotlin supporting ksp version makes this video still useful 👍
android development is getting better and faster
Thanks a lot. You're one of the best Android teachers!❤
Always up to date!
Thanks. Just few weeks ago I tried KSP but it seems it has problems with Dagger Hilt. There was warning saying something was not recognized. I'm glad that latest Dagger Hilt supports KSP.
@houssemzaier Hi, does the compose support Kotlin 1.9.0? I remembered I have to downgrade to 1.8.10
@phuang3 ye compose support 1.9
@@sudarshanbhatt9435 Tried kotlin 1.9.10 and KSP today. Too bad KSP doesn't support databinding anymore, so I have to include the kapt again...
@houssemzaier testing with hilt fails. any solution?
Thank you Philipp!
it would've been much better if you had display both kapt and ksp's build times
It's a free improvement without any downsides, I don't think it matters how much faster the build is as long as it is faster 😄
@Philipp let's say you want to keep databinding or something that doesn't support KSP yet, if we use Kapt for those and KSP for Room and Hilt, do we get some improvements in build times? or we only get faster builds if we give up on Kapt entirely?
complete ksp is faster as compiler don't have to wait for java stubs generation. if you use both then you won't get any significant changes to build time.
Google encourages the compose practices so they won't implement databinding to ksp.
Why when we adding ksp at top level gradle in the end we marked it like apply false?
you did good , the only downside is that the version for the hilt compiler and plugin is now 2.50 and the need of jvm in the project gradle file for it to work
i tried it and it work for debug, bug release build has minify issue.
@Philipp why you changed to compileOptions {
sourceCompatibility = JavaVersion.VERSION_18
Should I consider move away from JavaVersion.VERSION_1_8?
Thank you very much! Very interesting
how can we use KSP and Navigation component together? I get that error below;
Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
thats awesome!
Yup, Why does your face always appear in the recommendation list, you have the solution to the problem I'm facing... Thank you very much.
4:34 I hope the ai tool will help with this versioning and confusing configuration details some day soon
It’s a complete nightmare on android and needs to be addressed
It’s the most annoying thing on android!
Do you have any issues with hilt testing? I'm getting lots of error. I guess since this is the first supported version there are many issues with testing.
Are you using a beta or canary version of Android Studio? On the latest stable version AGP 8.2.xx is not supported like you show here.
Hey phillip, So I am using kotlin compiler version 1.9.10 and everything with KSP and other dependencies are set but when I try to implement Hilt dependencies just the ones you used here Im met with error "Unsupported class file major version 63"... Im using Hilt version 2.48.1
thank you
Can we use both in our project? KAPT and KSP?
this is did not work in my project. I had a problem with ksp failed in room to find some types of the properties. I think it is because i use classes generated by GraphQL Apollo library.
Thank you, usefull !
One point nine point zero point got point nice point video X)
Can you make an app and publish it with your own server in the computer ? Data is live
Super tip
Very goood !!!!!!!!
I'm getting this error and I couldn't solve it
Wow hilt support ksp now ..
Unfortunately if you use ksp with kapt e.g if you're using libraries that don't yet support ksp, then you'll still have slower build times and ksp will be useless at that time
Kind of retrofit? or else?
KSP still isn't useless - the more tools you have on KSP instead of KAPT the better state your build is in. However, it's true that you'll get the greatest improvement if you completely remove KAPT.
What libraries do you have that still need KAPT?
Can you use both ksp and kapt?
@@bidbid5413 Is that possible use both? ( I'm a beginer of KSP )
@@riyupapa39 yes
Greetings... If you have databinding, you must keep kapt :-(
Drop xml as soon as possible
It’s dead
Databinding is dead, but the scroll performance of Compose is too bad to fully drop XML @@ChrisAthanas
👍🙏
cool
Just FYI the video and audio is fairly degraded in this exported video... maybe check with your editor
Jay goram
I hate ksp many places it is simply not supported properly with unknown error thrown
cool tool
very far from my learning.
Nice, another clickbait. Claiming that it speeds up compilation without providing any examples/results.
Read the facts here: developer.android.com/build/migrate-to-ksp
You don't have to click on the videos :)
Some one needs a nap
sorry @TVHovna but you'll never be a grouchier Android dev than me. I'm the Winnebago Man of Android development
@@schrodingerscat3912 Android dev def brings out the grouchy
It's a huge pain in the ass
@@ChrisAthanas sorry guys but it's 101 of optimalization to measure before and after optimalizations are applied :D thumbnail is flashy and says that builds are up to 2 times faster, yet 0 proof or real observation is presented, therefore it is lying/misleading, not backing up serious claims. Do that to a client and you'll make yourself look like a dummy.
convert to KSP is successful , it' really faster
Still waiting for ksp to support retrofit 🥲
Why does Retrofit need support for KSP? Where do you use codegen with Retrofit?