Volodymyr Buberenko

> main.dart and sack.dart both are code from git Without a reproducer this bug report is not full. Can you run the plugin's example app?

> yes 🙃 Could you reply with more explanations? Still not reproducible code and if you can run example app it is highly likely something is wrong with your app.

It already works like that for non-Meta messangers, etc.. Regarding Facebook, etc. - check the README file as we mentioned that we don't have plans to implement support of their...

Would like to join the discussion here. First of all, thanks a lot for taking care of creating PRs for every plugin. I would like to not merge any of...

> I think it would be wonderful if the popular plus_plugins could support SPM as early as possible. Yes, it is a good point, but we are pretty quick to...

> it would be a good idea for packages containing iOS/macOS code to support SPM in advance. As I mentioned earlier as soon as there are no warnings or notes...

Hey @loic-sharma 👋🏻 Sorry, totally missed your comment and forgot that I didn't reply. Thank you very much for jumping here and reassuring that plugin authors have nothing to worry...

I have just released new versions with the support of SPM, so closing as resolved. Please try it out and provide feedback/PRs if you find any issues. Thanks to everyone...

Sounds like a great idea, so go ahead. I think I saw your tweets recently about `path_provider`. cc @miquelbeltran I think you might also be curios about it.

> FIX https://github.com/fluttercommunity/plus_plugins/issues/2966 The mentioned issue is about `package_info_plus`, while your changes are for `device_info_plus`. Could you explain why you did the change in this PR? `device_info_plus` supports a range...