altool Error: code -18000.

Question

Created Jul ’20

Replies 4

Boosts 0

Views 1.5k

Participants 4

Yesterday night, altool was working as usual.
Today, 9-July-2020, something has happened that is making altool unusual.
Seeing the following errors:

1 package(s) were not uploaded because they had problems:

/var/folders/mr/jn3hv6vd0336jzdx2f_4859r0000gp/T/22F0A966-FAE9-46CA-98C0-52310EF97E62/qtcorefw.itmsp - Error Messages:

Communication error. Please use diagnostic mode to check connectivity. You need to have outbound access to TCP port 443.

An exception has occurred: java.security.DigestException: partial digests not returned

Could not connect to Apple's web service.

2020-07-09 11:39:25.771 altool[3382:275147] * Error: Unable to notarize app.

2020-07-09 11:39:25.771 altool[3382:275147] * Error: code -18000 (Communication error. Please use diagnostic mode to check connectivity. You need to have outbound access to TCP port 443.)

2020-07-09 11:39:25.771 altool[3382:275147] * Error: code -18000 (An exception has occurred: java.security.DigestException: partial digests not returned)

2020-07-09 11:39:25.771 altool[3382:275147] * Error: code -18000 (Could not connect to Apple's web service.)

Answered by GabeJones in 621762022

I saw the same error as the OP when running XCode 12 beta 1 on macOS 11 DP2. When I updated to XCode 12 beta 2 the problem resolved.

Boost

Answer 1

DTS Engineer OP

Apple

Jul ’20

What version of Xcode are using? Specifically, if you run this:

Code Block  % xcode-select -p

it’ll print a path to your current Xcode. What version of Xcode is that?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 2

GabeJones OP

Jul ’20

Accepted Answer

I saw the same error as the OP when running XCode 12 beta 1 on macOS 11 DP2. When I updated to XCode 12 beta 2 the problem resolved.

1

Answer 3

jerrykrinock OP

Jul ’20

Thank you, GabeJones. It worked for me too. After failing with this error as described in the original post 5-10 times today, updating to Xcode 12 Beta 2 solved the problem.

0

Answer 4

ponca OP

Dec ’21

Sorry, I was away for a bit long time. The system I used went for a re-image. I do not remember the Xcode version and OS version at the time of reporting. I do not see the issue anymore with Xcode 13. I hope it was fixed later.

0