Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

161731384: Move to Picasso that has no support deps after it is released

See original GitHub issue

What feature would you like to see?

Right now you need to enable jetifier if you pull in the firebase-inappmessaging-display dependency as reported in #535 . This is due to a dependency on picasso which pulls in com.android.support:exifinterface:

com.android.support:exifinterface:27.1.0
\--- com.squareup.picasso:picasso:2.71828
     +--- debugCompileClasspath (requested com.squareup.picasso:picasso:{strictly 2.71828})
     \--- com.google.firebase:firebase-inappmessaging-display:19.0.7
          +--- debugCompileClasspath (requested com.google.firebase:firebase-inappmessaging-display)
          \--- com.google.firebase:firebase-bom:25.5.0
               \--- debugCompileClasspath

However, enabling jetifier, while undoubtedly handy in cases like these, unnecessarily slows down builds.

How would you use it?

I’d disable jetifier and enjoy faster builds. 🚀

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:15 (6 by maintainers)

Top GitHub Comments

6reactions

lordcodescommented, Oct 31, 2020

Rather than waiting you can use Gradle to force Picasso 2.8 to be used.

In Gradle Kotlin DSL:

implementation("com.squareup.picasso:picasso") {
    version {
        strictly("2.8")
    }
    because("Firebase In-App Messaging Display includes a Picasso version that doesn't use AndroidX")
}

3reactions

blundellcommented, Apr 12, 2021

Fixed in: https://github.com/firebase/firebase-android-sdk/pull/2408