-
Notifications
You must be signed in to change notification settings - Fork 109
Cannot access class 'kotlinx.datetime.Instant'. Check your module classpath for missing or conflicting dependencies #198
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
There's some extra configuration required for Android projects because old Android uses Java 1.6, but |
Thank you for your comment. I also followed the "Using in your projects" guide and set |
It doesn't look like an Android issue, since it's the implementation("org.jetbrains.kotlinx:kotlinx-datetime:0.3.2") to your dependencies and resyncing the Gradle project? |
Unfortunately the dependency has already been explicitly specified like that. I was just wondering if anybody else experienced this. |
I ran the build again but on command line with
a try and then it compiled. I certainly do not fully oversee all implications that (Sorry for kind of miss-using a bug ticket for this. Feel free to close this ticket anytime. I might sooner or later close this ticket myself if there are no other problems/ideas/comments.) |
|
Thanks for the explanation. I'm not writing a library and I'm not exposing anything from kotlinx-datetime. I'm actually just using |
I updated a bunch of dependencies in my multiplatform App project (Kotlin to 1.6.20, KotlinxSerialization to 1.3.2, ...) and after it the Android app started to have the problem:
Cannot access class 'kotlinx.datetime.Instant'. Check your module classpath for missing or conflicting dependencies
This error message is from Android Studio - I also updated Android Studio.
Strange enough it does compile ok for the iOS App with
gradle createXCFramework
. But my testscheme
in xCode also doesn't find theInstant
Kotlin class anymore.I wonder if this is only me or if anyone else has experienced this?
The text was updated successfully, but these errors were encountered: