GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — avoid dependency conflict between play-services and firebase · Issue #334 · fullstackreact/react-native-firestack Open DescriptionAs 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? ActivityMetadataMetadataAssigneesLabelsNo labels TypeProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |