bitrise-steplib / steps-xcode-build-for-simulator

MIT License
4 stars 18 forks source link

[BLOCKER] Unable to find simulator build in the artifact #44

Closed breadcomb-app closed 4 months ago

breadcomb-app commented 8 months ago

Troubleshooting

Useful information

Issue description

I'm building a simulator build for my application, however the logs shows it was built successfully, and the artifact is exported to the correct directory.

However, when I check the deploy to Bitrise.io logs, the .app build doesn't appear to be there.

Bitrise info

the log shows it's exporting artifact

      Copy artifacts from Derived Data to /Users/vagrant/deploy
      [REDACTED]Dev...
      Exporting outputs
      BITRISE_APP_DIR_PATH -> /Users/vagrant/deploy/[REDACTED]Dev.app
      BITRISE_APP_DIR_PATH_LIST -> /Users/vagrant/deploy/[REDACTED]Dev.app
      You can find the exported artifacts in: /Users/vagrant/deploy
  

but the deploy to bitrise doesn't show anything

      Build Artifact deployment mode: deploying the content of the deploy directory
      List of files to deploy (7):
      - /Users/vagrant/deploy/app-dev-debug.apk
      - /Users/vagrant/deploy/[REDACTED]Dev.dSYM.zip
      - /Users/vagrant/deploy/[REDACTED]Dev.ipa
      - /Users/vagrant/deploy/[REDACTED]Dev.xcarchive.zip
      - /Users/vagrant/deploy/export_options.plist
      - /Users/vagrant/deploy/xcodebuild-archive.log
      - /Users/vagrant/deploy/xcodebuild-export-archive.log
-   

Steps to reproduce

  1. build a normal react-native app
  2. add the Build for Simulator step in
lpusok commented 7 months ago

Hello, Please add the create-zip step after the build for simulator with the directory path $BITRISE_APP_DIR_PATH. This is a missing feature of build-for-simulator. The deploy step only picks up files, not directories.

bitrise-coresteps-bot commented 4 months ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented 4 months ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.