EAS build on main branch throwing a dirty working tree error

Description of the bug

eas build --platform ios --profile release --non-interactive --auto-submit
  shell: /usr/bin/bash -e {0}
  env:
    EXPO_TOKEN: ***

Warning! Your repository working tree is dirty.
This operation needs to be run on a clean working tree, please commit all your changes before proceeding.
    Error: Please commit all changes. Aborting...
Error: Process completed with exit code 1.

I am getting this error when following the docs. Any ideas on how this could be or how to fix it?

To Reproduce

What steps did you perform which led to this issue?

name: Expo Publish
on:
  push:
    branches:
      - production
  workflow_dispatch:

jobs:
  publish:
    name: Install and publish
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16.x
          cache: "npm"

      - uses: expo/expo-github-action@v6
        with:
          eas-version: latest
          expo-cache: true
          expo-version: 4.x
          token: ${{ secrets.EXPO_TOKEN }}

      - run: npm install
      - run: expo publish
      - run: eas build --platform ios --profile release --non-interactive --auto-submit

Expected behavior

The build would succeed.

Actual behavior

The build failed with the above error.

Additional context

See YAML.

[cvburgess]

That’s what I’m doing now, its just brittle with GitHub actions and protected branches: you need to use a personal token and when we did that we accidentally made a recursive set of commits that blew through our Actions quota for the month in ~15 minutes.

Its all working now but its an absolute pain for a small team unfamiliar with GHA (which I assume is a large part of the Expo userbase). Being able to pass this as a CLI arg would be amazing but I digress.

The “bug” here would be the way it shows up with two different version numbers in the EAS dashboard. If you do not support passing them the way I mentioned above, its very confusing to see that number appear in the builds list in EAS only to then see the build fail with an ominous message from apple upon submission. I would force both numbers in EAS to appear as the “true” build number to help people identify this a lot faster.

[cvburgess]

Im doing what @brentvatne said above. Its annoying but it works.

Be careful with protected branches.