Closed pheki closed 3 years ago
yes, it would be very nice, if you can update to FFI 1.0.
path_provider is in conflict to:
Because path_provider >=2.0.0 depends on path_provider_windows ^2.0.0 which depends on ffi ^1.0.0, path_provider >=2.0.0 requires ffi ^1.0.0.
And because flutter_sodium 0.1.11 depends on ffi ^0.1.3 and no versions of flutter_sodium match >0.1.11 <0.2.0, path_provider >=2.0.0 is incompatible with flutter_sodium ^0.1.11.
Working on it
And done, flutter_sodium 0.2.0 available in pub.dev
Nice, before i gave you a pull request today to support you. thanks :)
Also why not remove the Known Issues part now as FFI is stable now
Dart 2.12 has been released, and with it, both null safety and FFI are now stable.
I see that you have null-safety already in a pre-release, but can FFI be migrated as well? I can't update some of my dependencies (namely
shared_preferences
) as it depends on ffi 1.0Thanks a lot :)