After app store connect timeout, the step tries to retry but hangs forever

[micHar]

Troubleshooting

• [x] I've searched discuss.bitrise.io for possible solutions.
• Which version of the step is effected? 1.3.3
• Is the issue reproducible with the latest version? YES
• Does the issue happen sporadically, or every time? ONCE (hard to repeat)
• Is the issue reproducible locally by following our local debug guide? NOT APPLICABLE

Useful information

• FAQ
• devcenter.bitrise.io

Issue description

During the upload to ASC it failed to respond. The step assessed that it can retry the upload and tried to do that, called xcrun "altool"... but the build has been stuck at this for about an hour and never proceeded. It's difficult to reproduce, because it involves ASC timing out, but maybe you will be able to find something.

Bitrise info

• Bitrise Support enabled: NO_
• Log:

+------------------------------------------------------------------------------+

| (0) deploy-to-itunesconnect-application-loader@1                             |
+------------------------------------------------------------------------------+
| id: deploy-to-itunesconnect-application-loader                               |
| version: 1.3.3                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2022-01-31T13:02:50Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
Config:
- BitriseConnection: automatic
- AppleID: 
- Password: 
- AppSpecificPassword: 
- APIKeyPath: *****
- APIIssuer: xxx
- IpaPath: /Users/vagrant/deploy/xxx
- PkgPath: 
- Platform: auto
- ItunesConnectUser: 
- AdditionalParams: 
- BuildURL: xxx
- BuildAPIToken: *****

Bitrise Apple Developer Connection with API key found
Uploading - xxx ...
$ xcrun "altool" "--upload-app" "-f" "/Users/vagrant/deploy/xxx” "--type" "ios" "--apiKey" „xxx” "--apiIssuer" „xxx”
*** Error: *** retrieveUploadOperations: Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x60000188e610 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask .<1>"
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/buildDeliveryFiles, NSErrorFailingURLKey=https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/buildDeliveryFiles, _kCFStreamErrorDomainKey=4}

*** Error: Error uploading '/Users/vagrant/deploy/xxx’.
*** Error: The request timed out. (-1001)

Upload failed, but we recognized it as possibly recoverable error, retrying...
Uploading - xxx ...
$ xcrun "altool" "--upload-app" "-f" "/Users/vagrant/deploy/xxx” "--type" "ios" "--apiKey" „xxx” "--apiIssuer" „xxx”

//and nothing happened later
  

[manhpham90vn]

+1

[bitrise-coresteps-bot]

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]

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.