eas-cli
eas-cli copied to clipboard
hbc(bundle), hbc.map(sourcemap) file not existing on EAS Workflow
Build/Submit details page URL
No response
Summary
I need JS bundle and sourcemap file from 'update' workflow. When I run EAS Update locally on my PC, the files exist under dist/_expo/static/js/, but when I check within the update workflow using ls -la, no files are listed under the dist directory.
Here is my workflow.
name: Update Dev
on:
workflow_dispatch:
inputs:
message:
type: string
required: true
description: "change message"
jobs:
update_dev:
type: update
params:
message: "${{ inputs.message }}"
platform: all
branch: development
environment: development
upload_sourcemap:
needs: [update_dev]
steps:
- uses: eas/checkout
- name: get_sourcemap
run: |
ls -la
cd dist
ls -la
Managed or bare?
bare
Environment
expo-env-info
expo-env-info 1.3.4 environment info:
System:
OS: macOS 15.6
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.7.0 - /opt/homebrew/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.9.2 - /opt/homebrew/bin/npm
Watchman: 2025.06.30.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /Users/cupist/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12550806
Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
npmPackages:
expo: ~50.0.4 => 50.0.7
expo-router: ~3.4.6 => 3.4.7
expo-updates: ~0.24.13 => 0.24.13
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.73.2 => 0.73.2
react-native-web: ~0.19.6 => 0.19.10
npmGlobalPackages:
eas-cli: 16.17.4
Expo Workflow: bare
expo-doctor
env: load .env
env: export APP_ENV SINGULAR_APP_SECRET SINGULAR_API_KEY BYTEPLUS_TOKEN CHANNEL_TALK_PLUGIN_KEY API_URL AMPLITUDE_API_KEY SENDBIRD_APP_ID SENDBIRD_PROFILE_IMAGE_BASE_URL WEB_BASE_URL PROMOTION_BANNER_IMAGE_BASE_URL STATSIG_API_KEY BUGSNAG_API_KEY BYTEPLUS_PROJECT_ID BYTEPLUS_TENANT_ID
12/16 checks passed. 4 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.
✖ Check for issues with Metro config
It looks like that you are using a custom metro.config.js that does not extend "expo/metro-config". This can lead to unexpected and hard to debug issues. Learn more: https://docs.expo.dev/guides/customizing-metro/
Advice:
Update your metro.config.js to extend "expo/metro-config".
✖ Check dependencies for packages that should not be installed directly
The package "@types/react-native" should not be installed directly in your project, as types are included with the "react-native" package.
The package "expo-modules-core" should not be installed directly in your project. You should instead use the exported API from the expo package.
Advice:
Remove these packages from your package.json.
✖ Check for app config fields that may not be synced in a non-CNG project
This project contains native project folders but also has native configuration properties in app.config.ts, indicating it is configured to use Prebuild. When the android/ios folders are present, EAS Build will not sync the following properties: scheme, orientation, plugins, android, ios.
✖ Check that packages match versions required by installed Expo SDK
The following packages should be updated for best compatibility with the installed expo version:
@react-native-async-storage/[email protected] - expected version: 1.21.0
@react-native-masked-view/[email protected] - expected version: 0.3.0
[email protected] - expected version: ~50.0.20
[email protected] - expected version: ~13.10.6
[email protected] - expected version: ~15.4.6
[email protected] - expected version: ~3.3.12
[email protected] - expected version: ~16.0.9
[email protected] - expected version: ~3.4.10
[email protected] - expected version: ~0.26.5
[email protected] - expected version: 6.5.1
[email protected] - expected version: 0.73.6
[email protected] - expected version: ~1.8.0
[email protected] - expected version: 1.10.0
Your project may not work correctly until you install the correct versions of the packages.
Found outdated dependencies
Advice:
Use 'npx expo install --check' to review and upgrade your dependencies.
4 checks failed, indicating possible issues with the project.
Error output
No response
Reproducible demo or steps to reproduce from a blank project
executing Summary's workflow with eas workflow:run ./.eas/workflows/update-dev.yml