HTTP 401 issue

Question

Created 23h

Replies 1

Boosts 0

Participants 2

Hi, I have been notarizing my code for several years with the same procedure, but today I have the following message : Conducting pre-submission checks for FencingFox.zip and initiating connection to the Apple notary service... Error: HTTP status code: 401. Invalid credentials. Username or password is incorrect. Use the app-specific password generated at appleid.apple.com. Ensure that all authentication arguments are correct.

CloudKit query for FencingFox.pkg (1/00a276f170785e1dcbfbd6873a00b9309672338b) failed due to "Record not found". Could not find base64 encoded ticket in response for 1/00a276f170785e1dcbfbd6873a00b9309672338b The staple and validate action failed! Error 65.

I have changed my apple password and migrated to Sequoia. How should I investigate the issue ?

Boost

Answer 1

DTS Engineer OP

Apple

20h

Are you notarising from the command line? If so, I recommend that you run through the store-credentials workflow:

% xcrun notarytool store-credentials

This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name.
… and so on …

This interactively guides you through the credential process.

If you do this, what do you see?

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

0