The call to the iTMSTransporter completed with a non-zero exit status: 127. This indicates a failure. about fastlane

[mikemag-dev]

+1, seeing the same issue!

same password has been working fine before today. Issue started yesterday for me.

[lanceliamll]

@mikemag-dev have you updated some of gem file package versions? I either reverted it to previous versions and updated versions but still having the issue 2 weeks ago :(

[mikemag-dev]

not to my knowledge, we rarely update our CI tooling until something breaks. Perhaps it's some new auth apple requires which fastlane does not provide yet. I thought maybe it's because we're on fastlane 2.211.0, but per your description, updating to 2.212 would not help.

[lanceliamll]

@mikemag-dev let me know if you get thru this issue, thanks so much!

[lanceliamll]

@mikemag-dev have you updated xcode version?

[mikemag-dev]

@lanceliamll yep, using xcode 14.2 command line tools

[mikemag-dev]

@lanceliamll the issue seems to have resolved itself for my CD rerunning the same job this morning.

[ykhandelwal913]

@mikemag-dev This is still failing for us. Any changes you made to resolve this?

[mikemag-dev]

I'm no longer with the company where I was experiencing this with our CI, but there was a flag I changed which might have had an impact (no guarantees)

````ENV['ITMSTRANSPORTER_FORCE_ITMS_PACKAGE_UPLOAD'] = 'true'```
#20741 (comment)

However you should know, changing this flag caused an error with the upload phase where apple api was saying we'd already uploaded version/build x.y.z but we hadn't. That similarly prevented us from uploading to appstore connect