Android Studio cannot find Giphy SDK library during build

Other Questions Giphy
1

I’m having trouble integrating the Giphy SDK into my Android app. I followed the setup instructions but keep getting a dependency resolution error.

Here’s what I added to my project-level build.gradle:

repositories {
    maven {
        url "https://giphy.bintray.com/giphy-sdk"
    }
}

And in my app-level build.gradle:

implementation('com.giphy.sdk:core:1.0.0@aar') {
    transitive = true
}

When I try to sync the project, I get this error message:

Could not resolve: com.giphy.sdk:core:1.0.0

I’ve tried cleaning and rebuilding but the issue persists. What could be causing this dependency resolution problem?

2

Had this exact problem migrating an older project. That Bintray repo’s deprecated, but you’ll likely hit another issue even after switching to Maven Central. Check your Gradle wrapper version - older versions can’t resolve the newer Giphy SDK dependencies properly. I upgraded from gradle-7.0.2 to gradle-7.4.2 and it fixed everything. Also, if you’re targeting API 31+, make sure your compileSdk version is current. The Giphy SDK has compatibility requirements their docs don’t mention clearly. Your transitive flag should work fine once you fix the repository.

3

Yeah, the Bintray shutdown definitely broke your setup. This is exactly why I automated all my mobile builds - got tired of constantly fixing broken Gradle configs and hunting down new repo URLs.

I use Latenode workflows that handle everything: pulls latest SDK versions, manages dependencies, pushes builds to different environments. No more manual headaches.

Quick fix: switch to mavenCentral() and grab the latest Giphy SDK version. But seriously, automate this stuff. My workflows monitor SDK updates, test compatibility, and update projects automatically.

Saved me tons of debugging time. The mobile development templates in Latenode work great for this.

4

The issue you’re encountering is indeed due to the Bintray shutdown. Giphy has migrated to Maven Central, so you need to remove the custom maven repository and ensure that mavenCentral() is listed in your repositories. For your dependency, switch to implementation 'com.giphy.sdk:ui:2.3.13', as this is the current version of the UI SDK that contains the necessary components. Additionally, make sure to include implementation 'androidx.constraintlayout:constraintlayout:2.1.4' because the Giphy SDK requires it but may not always add it automatically. After making these changes, perform a clean build to resolve any lingering issues. The newer versions of the SDK tend to be more stable.

5

Hit this exact issue updating our mobile app last year. Bintray’s dead, but there’s another catch nobody’s mentioned.

Switch to mavenCentral() - that’s obvious. But the artifact name changed too. Don’t use com.giphy.sdk:core, use com.giphy.sdk:ui.

If you’ve got proguard enabled, check your rules. Giphy SDK needs specific keep rules or it breaks in release builds:

-keep class com.giphy.** { *; }
-dontwarn com.giphy.**

Spent half a day debugging production crashes because I missed this. Worked fine in debug, exploded on release.

Android 12+? Declare INTERNET permission explicitly. Some SDK versions handle the permission changes poorly.

6

hey, just a tip - bintray shut down back in 2021, so that repo link is dead. try using mavenCentral() and see if giphy updated their lib there. also, 1.0.0 seems kinda old, update it if you can!