-
Notifications
You must be signed in to change notification settings - Fork 278
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
Android Gradle Plugin 7.3 incompatible with device_calendar due to a transitive dependency flutter_native_timezone #483
Comments
Same issue here. The readme (https://github.com/builttoroam/device_calendar/tree/master#readme) refers to replacement of the apparently stale/deprecated package [flutter_native_timezone] (ref: pinkfish/flutter_native_timezone#53). There are many issue / PR references to "version 5" (going back ~6 months) which has not been released. The current version at time of writing being 4.3.1. Discussion of this issue appears to be here #474 |
I think I found that it's not going well. The package 4.3.1 in pub dev (https://pub.dev/packages/device_calendar) was pushed from master branch, not from 4.3.1 tag. For this reason, the two fellowing configuration don't give the same thing: device_calendar:
git:
url: https://github.com/builttoroam/device_calendar.git
ref: 4.3.1 device_calendar: ^4.3..1 Please push the right version of plugin on pub dev |
Any news on this? |
@VeryGiack a workaround is to use in your pubspec.yaml device_calendar:
git:
url: https://github.com/builttoroam/device_calendar.git
ref: 4.3.1 instead of device_calendar: ^4.3.1
cf . reason in my last comment #483 (comment) |
Hi @agacemi using:
give me this error:
|
Which version of kotlin you use ? This must be at least kotlin 1.6 |
Ohh thanks i was using 1.5.30, i'll try with 1.6 |
I've updated to kotlin 1.8.21 (current latest) and now it works, thx @agacemi |
Hi @thomassth or others... Any update on this? It would be good with a release (4.3.2 ?) that uses the The current version (4.3.1) is causing a lot of problems.... And we can't use the GitHub branch linked above, since we are using this |
If someone makes a PR I'll approve it Otherwise I don't have an estimate, and neither do any of the other maintainers it seems tbf most of us only became "maintainers" to push some PRs we had at the time, and if you wanna help maintain this package, check out the discussion topic and leave a note there |
@bardram @thomassth I would just to note that there is a workound by using gît tag 4.31 instead of using pub dev version 4.31. Cf. my comment above, i explain why. |
It works. but I think we need a patch fix version like 4.3.2 in pub.dev. |
I need someone other than me to create a PR so I can approve and merge. Can do both on my own. |
Seems like this has been fixed and merged now - now someone with publish access to pub.dev should publish a new version. Thanks. |
Would any maintainer please publish the new version? |
It has to be @nickrandolph |
@thomassth I tried emailing you re ownership of the repo. Get back to me, or DM on twitter, so we can unblock this |
Could any of the maintainers fork the repo and create another package that is properly updated? Also there is an update in the IOS calendar API for IOS17. I can't ask for calendar permission using the package but I don't know if it effects any other feature. |
For now, you can ask for iOS 17 specific permissions with flutter plugins that handles device permissions. I've DM'd nick, so we might have some news after the weekend. |
It seems like this issue has been fixed with release If so, this issue can be closed. |
Thank you I conform it fix the issue and thus can be closed. |
Describe the bug
When upgrading to AGP 7.3.x in order to use kotlin 1.8.x, build failed because of flutter_native_timezone used by device_calendar. flutter_native_timezone seems not be maintained et uses a very old version of kotlin
To Reproduce
Expected behavior
Flutter doctor
Run a
flutter doctor
so we can rule out env issuesThe text was updated successfully, but these errors were encountered: