fastlane: (Spaceship::Client::UnexpectedResponse) - 504 Gateway Time-out

New Issue Checklist

Updated fastlane to the latest version
I have read the Contribution Guidelines

Issue Description

Getting following error while executing sigh command for creating provisioning profile

/usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.27.2/lib/spaceship/client.rb:434 (Spaceship::Client::UnexpectedResponse)
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>Shield</center>
</body>
</html>

    from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.27.2/lib/spaceship/portal/portal_client.rb:332:in `provisioning_profiles'
    from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.27.2/lib/spaceship/portal/provisioning_profile.rb:246:in `all'
    from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.27.2/lib/spaceship/portal/provisioning_profile.rb:266:in `find_by_bundle_id'
    from /usr/local/lib/ruby/gems/2.3.0/gems/sigh-1.8.0/lib/sigh/runner.rb:68:in `fetch_profiles'
    from /usr/local/lib/ruby/gems/2.3.0/gems/sigh-1.8.0/lib/sigh/runner.rb:20:in `run'
    from /usr/local/lib/ruby/gems/2.3.0/gems/sigh-1.8.0/lib/sigh/manager.rb:7:in `start'
    from /usr/local/lib/ruby/gems/2.3.0/gems/sigh-1.8.0/bin/sigh:35:in `block (2 levels) in run'
    from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane_core-0.46.3/lib/fastlane_core/ui/fastlane_runner.rb:26:in `run!'
    from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /usr/local/lib/ruby/gems/2.3.0/gems/sigh-1.8.0/bin/sigh:99:in `run'
    from /usr/local/lib/ruby/gems/2.3.0/gems/sigh-1.8.0/bin/sigh:117:in `<top (required)>'
    from /usr/local/bin/sigh:23:in `load'
    from /usr/local/bin/sigh:23:in `<main>'

Configuration Files

Command executed:

sigh  -a com.xxx.xxxx -n pptestapp -q pptestapp.mobileprovision -u xxx@xxx.xxx

Environment

fastlane version:1.95.0

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 50 (10 by maintainers)

Most upvoted comments

Still happening for me (2016-08-27). Getting a mixture of error messages. Either “504 Gateway Time-out”, or a message about the apple developer website being down from maintenance. But checking https://developer.apple.com/system-status/ there doesn’t seem to be anything going on. Any ideas?

ERROR [2016-08-27 16:55:12.84]: Error finding relevant GitHub issues: undefined method `map' for nil:NilClass
/Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.10/lib/spaceship/client.rb:436:in `parse_response': [!] <?xml version="1.0" encoding="UTF-8"?> (Spaceship::Client::UnexpectedResponse)
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
     <key>resultCode</key>
     <integer>503</integer>
     <key>userString</key>
     <string>The Apple Developer website is undergoing maintenance. For details, visit developer.apple.com/system-status.</string>
     <key>resultString</key>
     <string>The Apple Developer website is undergoing maintenance. For details, visit developer.apple.com/system-status.</string>
     <key>httpCode</key>
     <integer>503</integer>
     <key>userLocale</key>
     <string>en_US</string>
  </dict>
</plist>

npomfret on Aug 27, 2016

This problem was solved just now. But I did not do anything. Maybe Apple has modified.

trsxxii on Jul 21, 2016

@npomfret The status page (for whatever reason) says every thing is fine but it definitely isn’t. The logged in account part of developer.apple.com is super slow and thats if it works at all. This has been happening to me both via match and the website for about 8 hours now.

reallistic on Aug 28, 2016

I’m getting this for the last 12 hours or so, but it’s intermittent - exactly the same run with exactly the same parameters on a completely clean source tree will pass sometimes and fail others. I think it may mainly be an issue at Apple’s end - might be nice if fastlane could pause and retry if it gets a 504 (if it doesn’t already).

jogu on Aug 11, 2016

Thank You @AcaiBowl @TKBurner @nolanwilson thanks for following up the issue and letting me know!

rohitkowadkar on Jul 22, 2016

Still 504 gateway time-out error occurs just now. Other causes??

trsxxii on Jun 20, 2016

Hi! I occurs the same issue. I Try again when WWDC finished.

trsxxii on Jun 17, 2016