Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"eas build:resign" failed because of GitHub? #2499

Closed
softlylove opened this issue Aug 17, 2024 · 3 comments
Closed

"eas build:resign" failed because of GitHub? #2499

softlylove opened this issue Aug 17, 2024 · 3 comments

Comments

@softlylove
Copy link

Build/Submit details page URL

No response

Summary

Hello, I encountered an error when running eas build:resign

Steps:

  1. Trigger a build on Expo Cloud.
  2. Register a new device after that build.
  3. Run eas build:resign, everything good until error occurred: Failed to resign build, because GitHub builds cannot be retried.

I have searched Discord, Documents, GitHub Issues and Google, no idea what happened exactly 🤔

image

Managed or bare?

Managed by Expo

Environment

expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 14.6.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.16.0 - ~/.nvm/versions/node/v20.16.0/bin/node
      npm: 10.8.1 - ~/.nvm/versions/node/v20.16.0/bin/npm
      Watchman: 2024.08.12.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
    IDEs:
      Xcode: 15.4/15F31d - /usr/bin/xcodebuild
    npmGlobalPackages:
      eas-cli: 10.2.3
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check npm/ yarn versions
✔ Check for issues with metro config
✔ Check for legacy global CLI installed locally
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK

Didn't find any issues with the project!

Error output

image

Reproducible demo or steps to reproduce from a blank project

  1. Trigger a build on Expo Cloud.
  2. Register a new device after that build.
  3. Run eas build:resign, everything good until error occurred: Failed to resign build, because GitHub builds cannot be retried.
@softlylove softlylove added the needs review Issue is ready to be reviewed by a maintainer label Aug 17, 2024
@szdziedzic
Copy link
Member

Failed to resign build, because GitHub builds cannot be retried

Hi,

Yeah, I think that's true we currently don't support retrying or resigning builds triggered by our GitHub trigger on the EAS side (meaning the retry option on a build page for GH builds is not available, but it is for builds triggered using CLI, and you can't do eas build:resign targeting GH builds).

The currently working retry mechanism for GH builds is through the GitHub UI
Screenshot 2024-08-19 at 12 34 35
but in reality, it will create a new build on the EAS side under the hood.

I believe we should add this information as a limitation to GitHub builds docs and make it more obvious in eas build:resign that you can't retry a given build because of XYZ when selecting it in an interactive select mode.

@szdziedzic szdziedzic added eas build and removed needs review Issue is ready to be reviewed by a maintainer labels Aug 19, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

@github-actions github-actions bot added the stale label Sep 19, 2024
Copy link

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants