Skip to content
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

Unable to use **permission_handler: ^8.1.4+2**. #146

Open
AnandSaran opened this issue Sep 2, 2021 · 4 comments
Open

Unable to use **permission_handler: ^8.1.4+2**. #146

AnandSaran opened this issue Sep 2, 2021 · 4 comments

Comments

@AnandSaran
Copy link

AnandSaran commented Sep 2, 2021

Unable to use permission_handler: ^8.1.4+2.
Getting following error.

Because google_maps_place_picker 2.0.0-nullsafety.3 depends on permission_handler ^6.0.1+1 and no versions of google_maps_place_picker match >2.0.0-nullsafety.3 <3.0.0, google_maps_place_picker ^2.0.0-nullsafety.3 requires permission_handler ^6.0.1+1.

If i use permission_handler: ^6.0.1+1 then no error.

@martin-braun
Copy link
Contributor

martin-braun commented Sep 3, 2021

You are not the first one reporting this, there are already enough PRs and issues (i.e. #88, #129, #123, #144) for that. If you can't wait for the fix, please check my fork that can be installed with flutter pub add as well, it's implementation is slightly changed to add some other functionalities to this project and fix the most issues with this repo. I made this fork, since the author doesn't have time apparently. I also contacted him through linked.in to hire him to extend this, without luck, so I took action and also published it myself to make a fix available for people like you.

Please do some search before you open the next issue on any repo, to prevent cluttering in general. Good luck with your project. :)

@Wian-TMC
Copy link

@martin-braun You're a champ for helping maintain this package with the latest package updates for geolocator and permission_handler

@martin-braun
Copy link
Contributor

@Wian-TMC You are welcome. :)

Feel free to open an issue on my fork if things need to be updated on my end (including error message details), I cannot check its build everyday, but I want to help nonetheless.

I also had some contact with @fysoul17 on linked.in, eventually. He is not able to take care of this repo in the near future, so my hope to pull from this repo someday in the future will be delayed.

@aqibaja
Copy link

aqibaja commented Apr 14, 2022

You can try same thing as #122 issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants