Skip to content
Latchkey

Heroku "Couldn't find that app" in CI

Heroku could not resolve the app you named. The -a value or the git remote points at an app that does not exist, was renamed, or is not accessible to the authenticated account.

What this error means

A Heroku command fails with "Couldn't find that app." or git push reports the app does not exist.

Heroku CLI
 ▸    Couldn't find that app.

Common causes

Wrong or renamed app name

The -a app name or the heroku git remote URL does not match an existing app, so Heroku cannot find it.

The account cannot access the app

The app exists but the authenticated account is not a collaborator or owner, so Heroku reports it as not found.

How to fix it

Pass the correct app name

  1. List apps with heroku apps to confirm the exact name.
  2. Pass it with -a or set the heroku git remote correctly.
  3. Confirm the account has access to the app.
Terminal
heroku apps:info -a my-app

Set the git remote to the right app

Point the heroku remote at the actual app so git-push deploys target it.

Terminal
heroku git:remote -a my-app

How to prevent it

  • Confirm the app name with heroku apps.
  • Keep the heroku git remote in sync with the app.
  • Use an account that has access to the app.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →