fastlane: [deliver] Could not find a build for app: ... on platform: ios
Issue Description
fastlane crashes on when uploading an app to the appstore. The app is uploaded correctly and fastlane crashes afterwards:
/.gem-cache/gems/fastlane-2.108.0/fastlane_core/lib/fastlane_core/ui/interface.rb:129:in `crash!': [!] Could not find a build for app: 1347102268 on platform: ios (FastlaneCore::Interface::FastlaneCrash)
Complete output when running fastlane, including the stack trace and command used
2018-11-14T10:00:07.1598200Z [11:00:07]: Successfully uploaded the new binary to App Store Connect 2018-11-14T10:00:07.1611920Z [11:00:07]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option 2018-11-14T10:00:08.6341860Z 2018-11-14T10:00:08.6357730Z Looking for related GitHub issues on fastlane/fastlane... 2018-11-14T10:00:08.6364750Z 2018-11-14T10:00:09.3527900Z Found no similar issues. To create a new issue, please visit: 2018-11-14T10:00:09.3542720Z https://github.com/fastlane/fastlane/issues/new 2018-11-14T10:00:09.3556200Z Run `fastlane env` to append the fastlane environment to your issue 2018-11-14T10:00:09.3573980Z [11:00:09]: WARNING: fastlane requires your locale to be set to UTF-8. To learn more go to https://docs.fastlane.tools/getting-started/ios/setup/#set-up-environment-variables 2018-11-14T10:00:09.3639210Z /Users/Company/.gem-cache/gems/fastlane-2.108.0/fastlane_core/lib/fastlane_core/ui/interface.rb:129:in `crash!': [!] Could not find a build for app: 1347102268 on platform: ios (FastlaneCore::Interface::FastlaneCrash) 2018-11-14T10:00:09.3662840Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing' 2018-11-14T10:00:09.3687710Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/fastlane_core/lib/fastlane_core/build_watcher.rb:13:in `wait_for_build_processing_to_be_complete' 2018-11-14T10:00:09.3711770Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/pilot/lib/pilot/build_manager.rb:55:in `upload' 2018-11-14T10:00:09.3732630Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/pilot/lib/pilot/commands_generator.rb:66:in `block (2 levels) in run' 2018-11-14T10:00:09.3753310Z from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call' 2018-11-14T10:00:09.3773730Z from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run' 2018-11-14T10:00:09.3806910Z from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command' 2018-11-14T10:00:09.3831380Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!' 2018-11-14T10:00:09.3858190Z from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!' 2018-11-14T10:00:09.3879530Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/pilot/lib/pilot/commands_generator.rb:166:in `run' 2018-11-14T10:00:09.3901340Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/pilot/lib/pilot/commands_generator.rb:18:in `start' 2018-11-14T10:00:09.3922870Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/fastlane/lib/fastlane/cli_tools_distributor.rb:100:in `take_off' 2018-11-14T10:00:09.3943960Z from /Users/Company/.gem-cache/gems/fastlane-2.108.0/bin/fastlane:23:in `<top (required)>' 2018-11-14T10:00:09.3963850Z from /usr/local/bin/fastlane:22:in `load' 2018-11-14T10:00:09.3983910Z from /usr/local/bin/fastlane:22:in `<main>' 2018-11-14T10:00:09.4098530Z ##[error]Error: fastlane failed with return code: 1
Environment
Fastlane-2.108.0
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 20 (5 by maintainers)
Haha, that I know - you posted it above. I was wondering if the people that replied that they have the same issue really do have the same issue with the same environment 😉
Are you all using Visual Studio DevOps: https://marketplace.visualstudio.com/items?itemName=ms-vsclient.app-store?
having this same issue, today…just updated fastlane to most recent immediately before running and having this issue.