search

bitrise-steplib / steps-deploy-to-itunesconnect-application-loader

MIT License
10 stars 13 forks source link

Unable to upload the IPA to app store connect. #50

Closed naninydhruva closed 5 months ago

naninydhruva commented 9 months ago

Hi ,

I am unable to update the ipa to app store connect after updating the xcode to 15 and set xcode build number step to 2.x.x version. it is shwoing follwoing error. 2024-02-10 08:28:29.410 altool[33709:1[REDACTED]867] -[NSCFNumber length]: unrecognized selector sent to instance 0x87bfd06d130bb5ab 2024-02-10 08:28:29.411 *** Error: ERROR: [ContentDelivery.Uploader] createRequestBuildCreateJsonWithResponse: caught an exception: -[NSCFNumber length]: unrecognized selector sent to instance 0x87bfd06d130bb5ab 2024-02-10 08:28:29.411 *** Error: Exception caught. -[NSCFNumber length]: unrecognized selector sent to instance 0x87bfd06d130bb5ab (-1010) { NSLocalizedDescription = "Exception caught."; NSLocalizedFailureReason = "-[NSCFNumber length]: unrecognized selector sent to instance 0x87bfd06d130bb5ab"; } Uploading IPA failed: exit status 1

kindly can anyone help us to resolve this error and let us know why this is occuirng.

bitrise-coresteps-bot commented 6 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 5 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.