-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VertexAi depending ktor 2, time to update? #6737
Comments
I found a few problems with this issue:
|
Hi @Curwe, thank you for reaching out. As mentioned in the comment here, upgrading a project to Ktor 3.0.0, will cause breaking changes because it will be a project level upgrade. We understand that Ktor 3.x.x will resolve the issue " I'll go ahead and mark this as a feature request. While we are unable to promise any timeline for this, we'll definitely keep this under our radar. P.S. For folks who find this useful, adding an emoji thumbs up on the original post can help us prioritize adding this to the roadmap. |
Thanks, happy about that :) |
Hello, I completely confirm this request. More and more libraries are now using Ktor 3, and therefore we cannot use this dependency without this update. |
[REQUIRED] Step 2: Describe your environment
Android Studio version: Meerkat Feature Drop Canary 7
Firebase Component: BOM, Crashlytics, Config, Messaging, Analytics and Vertexai
Component version: 33.10.0
Ktor version 3.1.1
Coil 3.1.0
[REQUIRED] Step 3: Describe the problem
Vertexai sdk is depending on a older version of ktor 2. And it makes apps running ktor 3 struggling.
I did read this on this closed issue #6413 that ktor 3 was to new and you want to wait, it's been a while now so I'll raise this issue again.
Steps to reproduce:
You can run the app with ktor 3 enabled. But as soon as I call
generativeModel.startChat()
the client crash withCaused by: java.lang.ClassNotFoundException: Didn't find class "io.ktor.client.plugins.HttpTimeout"
Hope this can be fixed in a soon rather then later release.
Cheers.
The text was updated successfully, but these errors were encountered: