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

Specified artifacts not showing on artifacts directory for local build #2522

Closed
davifelix5 opened this issue Aug 28, 2024 · 4 comments
Closed

Comments

@davifelix5
Copy link

Build/Submit details page URL

No response

Summary

When specifying build artifacts path on eas.json and setting EAS_LOCAL_BUILD_ARTIFACTS_DIR, the .dSYM.zip file do not appear on the specified directory when running eas build -p ios --local. The expected behavior is for the .dSYM.zip file and the generated folder to appear alongside the .ipa artifact, just as it happens with the downloaded artifacts on a remote build.

Managed or bare?

bare

Environment

expo-doctor:

Detailed check results:

The following packages should be updated for best compatibility with the installed expo version:
  [email protected] - expected version: ~51.0.31
  [email protected] - expected version: ~4.0.25
  [email protected] - expected version: ~1.12.15
  [email protected] - expected version: ~3.5.23
  [email protected] - expected version: ~0.25.24
  [email protected] - expected version: ~3.10.1
  [email protected] - expected version: ~51.0.4
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.

One or more checks failed, indicating possible issues with the project.

expo-env-info:

  expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 14.5
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
      npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
      Watchman: 2024.04.29.00 - /usr/local/bin/watchman
    Managers:
      CocoaPods: 1.15.2 - /Users/myuser/.rvm/gems/ruby-3.0.4/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:
      Android Studio: 2023.3 AI-233.14808.21.2331.11709847
      Xcode: 15.4/15F31d - /usr/bin/xcodebuild
    npmPackages:
      expo: ~51.0.26 => 51.0.26 
      expo-router: ~3.5.21 => 3.5.21 
      react: 18.2.0 => 18.2.0 
      react-dom: 18.2.0 => 18.2.0 
      react-native: 0.74.5 => 0.74.5 
      react-native-web: ~0.19.10 => 0.19.11 
    npmGlobalPackages:
      eas-cli: 11.0.2
    Expo Workflow: bare

Error output

No response

Reproducible demo or steps to reproduce from a blank project

  1. Create a expo project
  2. Install eas
  3. Create a eas.json file
{
    "build": {
        "production": {
            "ios": {
              "buildArtifactPaths": ["ios/build/*"]
            }
         }
     }
}
  1. Run EAS_LOCAL_BUILD_ARTIFACTS_DIR=$(pwd)/build eas build -p ios --local on the root of the project
  2. See that the the .dSYM.zip does not appear when running ls build.
@davifelix5 davifelix5 added the needs review Issue is ready to be reviewed by a maintainer label Aug 28, 2024
@szdziedzic szdziedzic added eas build issue accepted and removed needs review Issue is ready to be reviewed by a maintainer labels Aug 30, 2024
@szdziedzic
Copy link
Member

expo/eas-build#439

@expo-bot
Copy link
Contributor

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

szdziedzic added a commit to expo/eas-build that referenced this issue Sep 3, 2024
…rectory for local builds (#439)

# Why

expo/eas-cli#2522

Move build artifacts to the target build artifact directory for local builds. We currently only support this behavior for the application archive.

# How

Move build artifacts to the target build artifact directory for local builds.

# Test Plan

Tested manually using repro from expo/eas-cli#2522
@szdziedzic
Copy link
Member

It should be released as a part of 12.0.0

@davifelix5
Copy link
Author

It should be released as a part of 12.0.0

Thank you for the fast reply!

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

3 participants