-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
CRITICAL BUG using java.time.Instant which is not available in API below 26 #8
Comments
expect/actual would not solve this problem. You should be able to add the https://developer.android.com/studio/write/java8-support-table |
I've done it for the time being as I don't want latest version to crash on devices But since this is a navigation library I expected it to not rely on kotlinx datetime and work without desugaring I think that'd be a plus +1 |
I will look into including the Android Desugaring process in the library's build file for a future release. |
Why is using kotlin date time important...? |
The navigation events are timestamped:
It is possible that I can change the timestamp value from an |
This is addressed by the following PR and will the fix will be out in the next release: #10 |
Here are two exceptions , I updated the app with the library to min Sdk 21 and my users are getting this exception , I found this using Firebase Crashlytics
Since
https://stackoverflow.com/questions/52510370/java-lang-noclassdeffounderror-failed-resolution-of-ljava-time-localdate-erro
Please instead of using Kotlinx date time library to get the current time Millis , Use the expect actual functions , Please update the library as soon as possible , We have a lot of users who have this bug
The text was updated successfully, but these errors were encountered: