-
Notifications
You must be signed in to change notification settings - Fork 432
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
kotlinxDeserializerOf in fuel-kotlinx-serialization crashes with kotlin 1.3.70 and kotlinx.serialization 0.20.0 #720
Comments
Hmm, this might be a problem of a combination of version Kotlin + Kotlin serialization. Could you try this combination and see whether this works?
|
Those versions work fine (it's what I was using before). I upgraded to kotlin 1.3.70, which isn't compatible with kolinxSerialization 0.14.0, so I upgraded that to 0.20.0. Then these problems started occurring (so rolling back is a temporary solution). |
#722 I tried to update core version in this PR. I will try to bump to 1.3.70 and 0.20.0 🙇 |
FWIW I checked and it only breaks on specifically |
Hmm that is a bit concerning. So, if you provide a custom serializable adapter it would be just fine? |
So it's not actually the custom serializable adapter - it's the use of the So this crashes: But this does not: So it may be that just updating the libraries will fix the problem. Hope that helps. Thanks! |
I just ran into this same issue.
|
As a around until there's an update to the package, I ended up fixing by explicitly passing in a valid json configuration:
|
Looks good. Maybe you could make a shared |
Bug Report
Description
When using kotlin 1.3.70 and kotlinx.serialization 0.20.0,
kotlinxDeserializerOf
crashes on use. Kotlin 1.3.70 requires kotlinx.serialization 0.20.0.To Reproduce
Steps to reproduce the behavior:
kotlinxDeserializerOf
Expected behavior
Do not crash. Here is the stacktrace:
Environment
Development Machine
Complete the following information if applicable
Smartphone or Emulator
Complete the following information if applicable
The text was updated successfully, but these errors were encountered: