Android: Conflict after migrating to EAS

Hi,

we used to build the app with turtle-cli and a custom key store. We now migrated to EAS using a custom update server. Everything works fine, except for the app update on Android. When I have the old version and want to update to the new version, I get the error:

“The Package Conflicts With An Existing Package By The Same Name Error”

My credentials.json looks like this:

{
  "android": {
    "keystore": {
      "keystorePath": ".pathTo/keystore.jks",
      "keystorePassword": "keystorepassword",
      "keyAlias": "keyalias",
      "keyPassword": "keypassword"
    }
  },
  "ios": {
    "provisioningProfilePath": "pathTo/profile.mobileprovision",
    "distributionCertificate": {
      "path": "pathTo/cert.p12",
      "password": "password"
    }
  }
}

The values are correctly substituted and it works for iOS.

My EAS.json (I know, a lot of unecessary boilerplate):

{
  "cli": {
    "version": ">= 3.6.0"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "ios": {
        "resourceClass": "m1-medium",
        "credentialsSource": "local"
      },
      "android": {
        "credentialsSource": "local"
      },
      "channel": "development"
    },
    "preview": {
      "distribution": "internal",
      "ios": {
        "resourceClass": "m1-medium",
        "credentialsSource": "local"
      },
      "android": {
        "credentialsSource": "local"
      },
      "channel": "preview"
    },
    "production": {
      "ios": {
        "resourceClass": "m1-medium",
        "credentialsSource": "local"
      },
      "android": {
        "credentialsSource": "local"
      },
      "channel": "production"
    }
  },
  "submit": {
    "production": {}
  }
}

and we run the command (Azure DevOps pipeline)

eas build --platform android --non-interactive --local --output $(build.artifactstagingdirectory)/myfile.aab

When I then publish the .aab to Microsoft AppCenter and want to update, I get the error. If I delete the app, I can install it and also update it with newer versions from my build process.

Am I missing something?

Answering my own issue:
we generated an .aab using EAS. When uploading it to AppCenter, the .apk was generated by AppCenter therefore having a different certificate. After adding

"buildType": "apk"

as a property to “build” → “channel” → “android” in the eas.json and changing the output to “.apk” in the eas build command, it works now.

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.