expo / expo/eas-cli

Fingerprint step failing after `eas workflow:run` but works fine locally

Open
#3,034 3 comments 3 reactions 1 assignee Claimed by @sjchmiela View on GitHub
needs review
Dominant language
TypeScript
Stars
1.4k
Forks
236
Avg merge
3d 1h
Merged PRs (30d)
91

Description

### Build/Submit details page URL

_No response_

### Summary

In my project (on `Expo 52.0.46`), the "fingerprint" step in an eas workflow fails (`Error: fingerprint:generate command failed`) after running it with `eas workflow:run`, with the following error:

![Image](https://github.com/user-attachments/assets/788c75d6-da9b-491f-8627-1e103354791d)

Here's my workflow file:

```name: Deploy Android to production

jobs:
fingerprint:
name: Fingerprint
type: fingerprint
get_android_build:
name: Check for existing android build
needs: [fingerprint]
type: get-build
params:
fingerprint_hash: ${{ needs.fingerprint.outputs.android_fingerprint_hash }}
profile: production
build_android:
name: Build Android
needs: [get_android_build]
if: ${{ !needs.get_android_build.outputs.build_id }}
type: build
params:
platform: android
profile: production
submit_android_build:
name: Submit Android Build
needs: [build_android]
type: submit
params:
build_id: ${{ needs.build_android.outputs.build_id }}
publish_android_update:
name: Publish Android update
needs: [get_android_build]
if: ${{ needs.get_android_build.outputs.build_id }}
type: update
params:
branch: production
platform: android
```

Running `eas fingerprint:generate` locally works fine and successfully generates the fingerprint. I tried to repro the issue in a new, blank Expo 53 project but the fingerprint step actually works successfully after `eas workflow:run`.

Any ideas on how I might go about debugging or fixing this?

### Managed or bare?

Managed, CNG

### Environment

`npx expo-env-info`:

```expo-env-info 1.3.3 environment info:
System:
OS: macOS 14.7.5
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.7.0 - /opt/homebrew/bin/node
Yarn: 3.6.4 - /opt/homebrew/bin/yarn
npm: 10.9.2 - /opt/homebrew/bin/npm
Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.14.3 - /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
Android SDK:
API Levels: 28, 29, 30, 31, 33, 34, 35
Build Tools: 29.0.2, 30.0.2, 30.0.3, 33.0.0, 33.0.1, 34.0.0, 35.0.0
System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64, android-31 | Google APIs Intel x86 Atom_64, android-34 | Google Play ARM 64 v8a
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11330709
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmPackages:
expo: 52.0.46 => 52.0.46
expo-router: 4.0.5 => 4.0.5
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
react-native: 0.76.9 => 0.76.9
react-native-web: 0.19.13 => 0.19.13
npmGlobalPackages:
eas-cli: 16.6.2
Expo Workflow: bare
```

`npx expo-doctor`:

```13/15 checks passed. 2 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.

✖ Validate packages against React Native Directory package metadata
The following issues were found when validating your dependencies against React Native Directory:
Untested on New Architecture: react-native-receive-sharing-intent
Unmaintained: react-native-receive-sharing-intent
No metadata available: app, patch-package, postinstall-postinstall
Advice:
Use libraries that are actively maintained and support the New Architecture. Find alternative libraries with https://reactnative.directory.
Add packages to expo.doctor.reactNativeDirectoryCheck.exclude in package.json to selectively skip validations, if the warning is not relevant.
Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

✖ Check that packages match versions required by installed Expo SDK
The following packages should be updated for best compatibility with the installed expo version:
@sentry/react-native@6.14.0 - expected version: ~6.10.0
@shopify/flash-list@1.7.1 - expected version: 1.7.3
expo-av@15.0.1 - expected version: ~15.0.2
expo-build-properties@0.13.2 - expected version: ~0.13.3
expo-clipboard@7.0.0 - expected version: ~7.0.1
expo-constants@17.0.5 - expected version: ~17.0.8
expo-document-picker@13.0.1 - expected version: ~13.0.3
expo-file-system@18.0.3 - expected version: ~18.0.12
expo-font@13.0.3 - expected version: ~13.0.4
expo-image@2.0.0 - expected version: ~2.0.7
expo-linear-gradient@14.0.1 - expected version: ~14.0.2
expo-linking@7.0.2 - expected version: ~7.0.5
expo-network@7.0.0 - expected version: ~7.0.5
expo-router@4.0.5 - expected version: ~4.0.21
expo-splash-screen@0.29.21 - expected version: ~0.29.24
expo-status-bar@2.0.0 - expected version: ~2.0.1
expo-store-review@8.0.0 - expected version: ~8.0.1
expo-system-ui@4.0.8 - expected version: ~4.0.9
expo-web-browser@14.0.1 - expected version: ~14.0.2
react-native-screens@4.0.0 - expected version: ~4.4.0
react-native-webview@13.13.5 - expected version: 13.12.5
jest-expo@52.0.3 - expected version: ~52.0.6
react-native-screens@4.0.0 - expected version: ^4.0.0
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies
Advice:
Use 'npx expo install --check' to review and upgrade your dependencies.

2 checks failed, indicating possible issues with the project.
```

### Error output

_No response_

### Reproducible demo or steps to reproduce from a blank project

N/A (see above, unable to repro in a blank project)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.