EAS Android Build Failure

Expo Application Services (EAS)
1

In your post, please share:

  • managed workflow
  • Your eas-cli version: 0.52.0

Hi all!

EAS build Android works fine in the past week but suddenly here is the failture message in gradlew out of the blue no matter what I tried:

image
image1410×860 34.1 KB

I suppose it is nothing wrong with EAS, it build iOS just fine. Here is the dependency I installed: "@wowmaking/react-native-iron-source": "^7.0.4",

Also, here is the plugin:

const { withAppBuildGradle } = require("@expo/config-plugins");

module.exports = function dependenciesPlugin(expoConfig) {
  return withAppBuildGradle(expoConfig, async (config) => {
    config.modResults.contents = applyImplementation(
      config.modResults.contents
    );
    return config;
  });
};

function applyImplementation(appBuildGradle) {
  const dependenciesImplementation = `
  implementation 'com.ironsource.sdk:mediationsdk:7.2.3.1' 
  implementation 'com.ironsource.adapters:adcolonyadapter:4.3.12'
  implementation 'com.adcolony:sdk:4.7.1'
  implementation 'com.ironsource.adapters:applovinadapter:4.3.33'
  implementation 'com.applovin:applovin-sdk:11.4.4'
  implementation 'com.ironsource.adapters:facebookadapter:4.3.36'
  implementation 'com.facebook.android:audience-network-sdk:6.11.0'
  implementation 'com.ironsource.adapters:inmobiadapter:4.3.15' 
  implementation 'com.inmobi.monetization:inmobi-ads:10.0.8' 
  implementation 'com.ironsource.adapters:mytargetadapter:4.1.13'
  implementation 'com.my.target:mytarget-sdk:5.15.0'
  implementation 'com.google.android.exoplayer:exoplayer-core:2.13.3'
  implementation 'com.google.android.exoplayer:exoplayer-hls:2.13.3'
  implementation 'com.my.tracker:mytracker-sdk:3.0.0'
  implementation 'com.ironsource.adapters:pangleadapter:4.3.14'
  implementation 'com.pangle.global:ads-sdk:4.5.0.4'
  `;

  // Make sure the project does not have the dependency already
  if (!appBuildGradle.includes(dependenciesImplementation)) {
    return appBuildGradle.replace(
      /dependencies\s?{/,
      `
      repositories {
        mavenCentral()
        maven {url 'https://android-sdk.is.com/'} 
        maven {url 'https://artifact.bytedance.com/repository/pangle'}     
     }
     
      dependencies {
    ${dependenciesImplementation}`
    );
  }

  return appBuildGradle;
}

Please let me know if you have any ideas / direction on what is going on. Many thanks!

2

hello! you’d probably have best success going to the repository that is related to the error: GitHub - wowmaking/react-native-iron-source: Iron Source SDK React Native bridge

this issue seems related: Android build error · Issue #88 · wowmaking/react-native-iron-source · GitHub

3

Your config plugin adds https://android-sdk.is.com to the repositories, so I think that should allow Gradle to find what it needs, unless there’s something wrong with that repository at the moment.

I don’t know much about Gradle and/or Maven, but I think there is indeed a problem with the https://android-sdk.is.com/ repository.

If I try to get it manually with mvn like this:

mvn dependency:get -DremoteRepositories=https://android-sdk.is.com/ -DgroupId=com.ironsource.sdk -DartifactId=mediationsdk -Dversion=7.0.4 -Dtransitive=false

I get the following output:

[...]
[INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ standalone-pom ---
[INFO] Resolving com.ironsource.sdk:mediationsdk:jar:7.0.4
Downloading from central: https://repo.maven.apache.org/maven2/com/ironsource/sdk/mediationsdk/7.0.4/mediationsdk-7.0.4.jar
Downloading from temp: https://android-sdk.is.com/com/ironsource/sdk/mediationsdk/7.0.4/mediationsdk-7.0.4.jar
[...]

If I try to fetch the android-sdk.is.com URL above (and the corresponding .pom file), I find this:

This exists: https://android-sdk.is.com/com/ironsource/sdk/mediationsdk/7.0.4/mediationsdk-7.0.4.pom
This does not: https://android-sdk.is.com/com/ironsource/sdk/mediationsdk/7.0.4/mediationsdk-7.0.4.jar

So I think that’s why you’re having a problem and as far as I can tell it is something that IronSource needs to fix.

You might be able to work around it if you set up your own Maven repository and add it to build.gradle and manually get hold of the JAR file and add it to your repository :man_shrugging:

4

Thank you very much @wodin and @brents ! I have reported to IronSource, and let see how it goes!