You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First I must say, that you do a great job and I appreciate your plugin and your work.
Each Time Flutter updates its intl we stick a long time to the intl 0.19.0 due the fact that easy_localization references to flutter_localization, which is not compatible with the intl 0.19.0 for a long time and gets updated late after its release.
Would it be possible that the easy_localizaiton plugin does not anymore needs flutter_localization and works without its reference and be able to be upgraded independently?
Many Thanks for your thoughts
Roman
The text was updated successfully, but these errors were encountered:
I’m currently facing a version conflict issue between easy_localization and awesome_notifications. I’m using a pinned version easy_localization: ^0.19.0, but awesome_notifications requires easy_localization >=0.20.0. Due to this, I’m unable to update without breaking compatibility.
I’m in a situation where I either have to drop one of the plugins and lose important features or find a workaround. I’ve already tried various solutions, including consulting ChatGPT, but haven’t been able to resolve it.
A fix or suggestion from the team would be incredibly helpful for developers like me who rely on both plugins.
Hello Dev Team,
First I must say, that you do a great job and I appreciate your plugin and your work.
Each Time Flutter updates its intl we stick a long time to the intl 0.19.0 due the fact that easy_localization references to flutter_localization, which is not compatible with the intl 0.19.0 for a long time and gets updated late after its release.
Would it be possible that the easy_localizaiton plugin does not anymore needs flutter_localization and works without its reference and be able to be upgraded independently?
Many Thanks for your thoughts
Roman
The text was updated successfully, but these errors were encountered: