expo / expo/eas-cli

Subsmission webhook not firing and I don't know how to debug it

Open
#2,974 2 comments 1 reaction 0 assignees 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

https://expo.dev/accounts/drilldown/projects/tuduu/submissions/f37dd8d6-cbd6-4c4c-9dab-8833c5944170

### Summary

I implemented a submission WebHook following the Expo guide and deployed it to our test environment. Testing it with the sample payload works correctly. However, the **WebHook is never triggered during actual submissions.**

### Managed or bare?

Managed

### Environment

expo-env-info 1.2.2 environment info:
System:
OS: macOS 15.4
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.7.0 - /opt/homebrew/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 11.2.0 - /opt/homebrew/bin/npm
Watchman: 2025.02.17.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
IDEs:
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
expo: ~52.0.38 => 52.0.38
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
react-native: 0.76.7 => 0.76.7
react-native-web: ^0.19.13 => 0.19.13
npmGlobalPackages:
eas-cli: 13.2.0
Expo Workflow: managed

---

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: @kichiyaki/react-native-barcode-generator, react-native-confetti-cannon
Unmaintained: @gorhom/portal, @kichiyaki/react-native-barcode-generator, expo-random, react-native-confetti-cannon, react-native-parsed-text
No metadata available: @expo/config-plugins, @tanstack/query-async-storage-persister, @tanstack/react-query-persist-client, firebase, immer, react-native-app-link
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:
expo@52.0.38 - expected version: ~52.0.42
expo-dev-client@5.0.14 - expected version: ~5.0.16
expo-file-system@18.0.11 - expected version: ~18.0.12
expo-image@2.0.6 - expected version: ~2.0.7
react-native@0.76.7 - expected version: 0.76.8
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies

### Error output

_No response_

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

I followed the guide here: https://docs.expo.dev/eas/webhooks/ to implement a submission WebHook to be notified when a submission is completed. The API I implemented is testable here, on our temporary test environment: `https://tuduu-tst-unifiedophub-func.azurewebsites.net/api/ExpoSubmissionsToSlack?code=github_issue_istance_temp_key`.

When I test it with the documentation payload, it works fine.

```json
{
"id": "0374430d-7776-44ad-be7d-8513629adc54",
"accountName": "dsokal",
"projectName": "example",
"submissionDetailsPageUrl": "https://expo.dev/accounts/dsokal/projects/example/builds/0374430d-7776-44ad-be7d-8513629adc54",
"parentSubmissionId": "75ac0be7-0d90-46d5-80ec-9423fa0aaa6b", // available for submission retries
"appId": "23c0e405-d282-4399-b280-5689c3e1ea85",
"archiveUrl": "http://archive.url/abc.apk",
"initiatingUserId": "7bee4c21-3eaa-4011-a0fd-3678b6537f47",
"cancelingUserId": null, // available for canceled submissions
"turtleBuildId": "8c84111e-6d39-449c-9895-071d85fd3e61", // available when submitting a build from EAS
"platform": "android", // or "ios"
"status": "errored", // or: "finished", "canceled"
"submissionInfo": {
// available for failed submissions
"error": {
"message": "Android version code needs to be updated",
"errorCode": "SUBMISSION_SERVICE_ANDROID_OLD_VERSION_CODE_ERROR"
},
"logsUrl": "https://submission-service-logs.s3-us-west-1.amazonaws.com/production/submission_728aa20b-f7a9-4da7-9b64-39911d427b19.txt"
},
"createdAt": "2021-11-24T10:15:32.822Z",
"updatedAt": "2021-11-24T10:17:32.822Z",
"completedAt": "2021-11-24T10:17:32.822Z",
"maxRetryTimeMinutes": 3600 // max retry time for failed/canceled submissions
}
```

Well, the API is never being called. I have some loggers, but I don't see anything, although I correctly see it configured here:

Image

How can I debug this?

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.