Conversation
|
If this solution is correct, could you please approve this PR? |
|
yes this is correct solution |
|
|
I got lost here... is it a solution or not?
|
|
add this in your pubspec ymail in ypur project |
|
@matanshukry pls review this one |
|
Hi @ahmedfayed29, @lecaro and @matanshukry, I’ve been following this PR and the discussions in #105 and #128. It's clear that there is community consensus on these fixes, but we are all stuck waiting for an approval. @matanshukry, we understand you might be busy, but with the Google Places SDK CocoaPods deprecation (Q2 2026) and the mandatory move to the Places API (New), this package is at a critical crossroads. I am willing to contribute the full iOS migration to Swift/SPM using Pigeon, which would solve the pending issues with locale and the new API requirements. However, I’m hesitant to start such a massive refactor if PRs like this one (#135) are not being reviewed or merged. Can we get an update on the project's status? If you need help, I’m sure many of us here would be happy to step up as co-maintainers to keep this plugin alive and compliant with Google's 2026 standards. Otherwise, we might be forced to consolidate these efforts into a community fork to avoid project stagnation." |
|
Since this repository appears to be inactive and the Google Places API (Legacy) deprecation is approaching, I’ve created a maintained fork to merge pending PRs and add critical updates needed for modern Flutter projects. My primary goal is to keep the community unblocked. If the original author returns, I would be more than happy to merge all these improvements back into this repository. In the meantime, I have published the updated package as
🚀 Key Improvements in this Fork:
I will be actively maintaining this version and I'm happy to help with any issues or PRs. Feel free to give it a try! |
issue in build for android as for using useNewApi
and also for using old dependancies