Dependency on play-services or firebase 11.4.2+ breaks the build
See original GitHub issueThere are some new dependencies like com.google.android.gms:play-services-tasks-license
that appear to be aar
files but do not contain a jar
within, only some txt and xml files. This breaks the build as the javadoc plugin (and possibly other things) expect at least an empty jar.
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Release Notes | Firebase - Google
This release includes dependency updates in Cloud Firestore and new features in the Authentication API. ... Breaking: Moves standalone builds to Node.js 16....
Read more >How to compile play-services:11.2.0 [duplicate] - Stack Overflow
Selective compile is better option instead of complete play-services artifacts, you should choose what you needed in your project. compile 'com.
Read more >Release Notes - Play services - Google Developers
Updates the Google Mobile Ads Android SDK and Firebase Ads SDK. ... Add the following to the dependencies section of your build.gradle :....
Read more >firebase_messaging | Flutter Package - Pub.dev
Flutter plugin for Firebase Cloud Messaging, a cross-platform messaging solution that ... BREAKING BUILD: set osx min supported platform version to 10.12.
Read more >Firestore conflict. - Google Groups
I have a project where i use Google Cloud Speech, and Firebase RealTime ... dependencies { classpath 'com.android.tools.build:gradle:3.0.0' classpath ...
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
Yeah they play nice together but I can’t actually build a version of geofire that has 11.6.0 as its stated dependency because of something maven tries to do in the releasing step.
I’ve filed a bug internally to work on this.
Fixed in
2.3.1