-
Notifications
You must be signed in to change notification settings - Fork 110
uses wrong name for kotlinx-serialization module with legacy compiler #118
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
Comments
Thanks for raising this, your reproducer is great! Yes, either rebuilding the datetime library with dependency on |
It looks like this is the cause https://youtrack.jetbrains.com/issue/KT-43237 so my interpretation is that there is now an incompatibility between modules published with 1.4 and 1.5 |
* This fixes the incompatibility with the newer serialization versions. * Upgraded the version of kotlinx.serialization. * watchosX64 target is added. Fixes #118
* This fixes the incompatibility with the newer serialization versions. * watchosX64 target can now be added. Fixes #118
repo demonstrating issue: https://github.com/ethanmdavidson/serializationNameBug
When using the legacy compiler, kotlinx-datetime uses an old name when referencing kotlinx-serialization: 'kotlinx-serialization-kotlinx-serialization-core-jsLegacy' instead of 'kotlinx-serialization-kotlinx-serialization-core-js-legacy'.
May be related to https://youtrack.jetbrains.com/issue/KT-46598
I think it might be fixed by simply upgrading kotlinx.serialization to 1.2.1 (latest version)
The text was updated successfully, but these errors were encountered: