First submission to google

[oxott]

I am using eas-cli/3.6.0 win32-x64 node-v16.13.0 - managed workflow.

I have tried to follow the documentation about the first submit to google.
As described here:
https://docs.expo.dev/submit/android/#manually-uploading-your-app-for-the-first-time

I could not find any documentation of how to build an aab (app-bundle) with expo. So I looked at the android page for some help https://developer.android.com/studio/build/building-cmdline#build_bundle and came to that configuration (eas.json):

{
  "cli": {
    "version": ">= 3.5.1"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "ios": {
        "resourceClass": "m1-medium"
      },
      "android" : {
        "buildType" : "app-bundle",
        "gradleCommand": ":app:bundleDebug"
      }
    },
    "preview": {
      "distribution": "internal",
      "ios": {
        "resourceClass": "m1-medium"
      },
      "android" : {
        "buildType" : "app-bundle",
        "gradleCommand": ":app:bundleDebug"
      }
    },
    "production": {
      "ios": {
        "resourceClass": "m1-medium"
      }
    }
  },
  "submit": {
    "production": {}
  }
}

that allowed me to produce an app-bundle, running

eas build -p android -e development

or

eas build -p android -e preview

If I try to upload it to google, I get the error message “The android app bundle is not signed”.

All the documentation i see references expo build:android, wich is no longer supported.

[wodin]

Hi @oxott

The default eas.json looks like this:

{
  "cli": {
    "version": ">= 3.7.2"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "ios": {
        "resourceClass": "m1-medium"
      }
    },
    "preview": {
      "distribution": "internal",
      "ios": {
        "resourceClass": "m1-medium"
      }
    },
    "production": {
      "ios": {
        "resourceClass": "m1-medium"
      }
    }
  },
  "submit": {
    "production": {}
  }
}

The above config does this:

• “development” profile: APK, debug
• “preview” profile: APK, production
• “production” profile: app bundle, production

You can of course override those defaults, but you probably don’t want to.

Both the development and preview builds are meant to be installed on an emulator or side loaded onto a physical device. This is why they are APKs.

The development build is of course for development purposes, so it’s built in debug mode.

The preview build is supposed to be basically like the production build, so it’s built in production mode.

The app bundle that you get from building with the “production” profile is what you should be uploading to the Google Play Store.