Feature request: Compatibility with Google Play services 9.x.x
See original GitHub issueDo not force consumers to use latest Play services library.
Since this project started at 9.0.0 let’s assume that this is the actual minimum.
Same goes for support library. Google play services need at least 24.0.0 so that should be minimum.
Dependencies on Facebook and Twitter SDK should be provided
instead of compile
(if applicable).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Set up Google Play services
To develop features that depend on the Google Play services APIs in your app, complete the following steps: Open the build.gradle file inside...
Read more >Meet Google Play's target API level requirement
When you upload an APK, it must meet Google Play's target API level requirements. New apps must target Android 12 (API level 31)...
Read more >Keep your device & apps working with Google Play Services
Step 1: Make sure Google Play Services is up to date · On your Android phone or tablet, open the Settings app Settings...
Read more >How to Update Google Play Services on Your Android Phone
1. Start the Settings app on your Android phone. · 2. Tap "Apps & Notifications." If your Android device doesn't have this option,...
Read more >Google Play services discontinuing updates for Jelly Bean ...
This results in increased developer and QA time spent on new features that require special handling. Consequently, we are deprecating support ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@samtstern I come from old school (i.e. market) where people are reluctant to update apps (incl. Google Play services) or have disabled automatic updates. It used to be about lack of space, now it’s about conserving data.
Unless it’s absolutely necessary we don’t want to bother users with updating an external app (GMS), even more so when the core app does not leverage any new features of 10.0.x (but can still leverage security fixes if a newer version is installed on the device, right?).
Encourage - yes. Force - no.
I am going through old issues and I am going to close this one. Although I totally understand the benefit the opposite request is much more common: users want to use a newer version of play services with an older version of FirebaseUI. In general it’s much more aligned with the goals of this library to depend on the latest library version which has all new features, bugfixes, etc.
We do plan to move over to the new gradle
implementation
designation soon, which may help here.Thank you @consp1racy for filing originally, it inspired some good conversations.