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

avoid dependency conflict between play-services and firebase #334

Open
haraldreingruber opened this issue Apr 26, 2017 · 2 comments
Open

Comments

@haraldreingruber
Copy link

As this seems to be a recurring issue, I would like to trigger a discussion about how this problem can best be mitigated for the future.

There are already several PRs offering different solutions (#323, #332 and #290), and according to #134 some users have other depending libraries which include a version (or the latest version?) of play-services on their own.

To my opinion, the most important thing is that the versions of these dependencies are consistent. So, I would be in favor of either setting all to a fixed version (#332), or all to the latest version (#323). Of course, if we set all to latest, life might be easier for users who have other dependencies to play-services...

What do you think?

@Salakar
Copy link
Collaborator

Salakar commented May 3, 2017

Wrote some docs on that here as it's generally a common issue

@haraldreingruber
Copy link
Author

@Salakar: thanks for the hint.

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

2 participants