Post

Replies

Boosts

Views

Activity

Reply to altool fails with "The auth server returned a bad status code"
Hi, This error is coming often now. I have tried the following command it is giving output. xcrun altool --list-providers --username "username" --password "@keychain:NOTARIZE_PASSWORD" I am using app specific password generated for my user name. I got the following output for the above command. 2022-01-31 14:55:51.693 altool[99127:17893146] CFURLRequestSetHTTPCookieStorageAcceptPolicy_block_invoke: no longer implemented and should not be called ProviderName ProviderShortname PublicID                             WWDRTeamID  ------------ ----------------- ------------------------------------ ----------  xxxxx      xxxx            69a6de70-xxxxx-xxxxxx-xxxxxxxxx 82xxxxxxxxC  macOS: 11.0.1 Xcode: 12.3 regards Prema Kumar
Jan ’22
Reply to After changing the Apple ID password, app specific passwords are not working even after creating new app specific password
Hi Quinn, Following command also fails xcrun notarytool store-credentials NOTARY_TOOL_PASS --apple-id Apple_ID --team-id team_ID --password app-specific-password This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name. Validating your credentials... 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. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Jun ’22
Reply to altool fails with "The auth server returned a bad status code"
Hi, This error is coming often now. I have tried the following command it is giving output. xcrun altool --list-providers --username "username" --password "@keychain:NOTARIZE_PASSWORD" I am using app specific password generated for my user name. I got the following output for the above command. 2022-01-31 14:55:51.693 altool[99127:17893146] CFURLRequestSetHTTPCookieStorageAcceptPolicy_block_invoke: no longer implemented and should not be called ProviderName ProviderShortname PublicID                             WWDRTeamID  ------------ ----------------- ------------------------------------ ----------  xxxxx      xxxx            69a6de70-xxxxx-xxxxxx-xxxxxxxxx 82xxxxxxxxC  macOS: 11.0.1 Xcode: 12.3 regards Prema Kumar
Replies
Boosts
Views
Activity
Jan ’22
Reply to After changing the Apple ID password, app specific passwords are not working even after creating new app specific password
Hi, Please help. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jun ’22
Reply to After changing the Apple ID password, app specific passwords are not working even after creating new app specific password
Hi Quinn, We have plans to upgrade to new tool. But not at this point of time. I have raised a request 101713929100. Regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jun ’22
Reply to After changing the Apple ID password, app specific passwords are not working even after creating new app specific password
Hi Quinn, Following command also fails xcrun notarytool store-credentials NOTARY_TOOL_PASS --apple-id Apple_ID --team-id team_ID --password app-specific-password This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name. Validating your credentials... 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. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jun ’22
Reply to Notarization error : Error -18000: org.apache.http.conn.HttpHostConnectException
Hi, Any insight? This is happening in some builds. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization error : Error -18000: org.apache.http.conn.HttpHostConnectException
Hi Quinn, Thank you for the reply. The current production systems are using altool, We are in the process of migration to notarytool. I need to make this (altool) working as our product releases are on hold. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization error : Error -18000: org.apache.http.conn.HttpHostConnectException
Hi Quinn, Yes 95% of time it is failing. Attached is the error we see when we do a trace root from office network. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization error : Error -18000: org.apache.http.conn.HttpHostConnectException
Hi Quinn, it was a firewall issue in our side. Network team was getting the following error. Connection terminated before detection: Insufficient data passed.To learn more see sk113479. Regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization error : Error -18000: org.apache.http.conn.HttpHostConnectException
Hi, Just to clarify, altool command was looking for some new ports to be opened. That was the reason of the failure. Not sure something has changed from Apple side. regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to altool fails with "The auth server returned a bad status code"
Hi, This error is happening again. I have reported this in FB10806063. Please help. it is blocking everything we do. I am using app specific password. Upgrading to noratytool is in our list, and we will do it. regards Prema Kumar
Replies
Boosts
Views
Activity
Jul ’22
Reply to altool fails with "The auth server returned a bad status code"
Hi @Quinn, I have uploaded the --verbose command output in the bug report. Please check. regards Prema Kumar
Replies
Boosts
Views
Activity
Jul ’22
Reply to A timestamp was expected but was not found
Hi,  This issue is happening from this week. It works sometimes. Both Codesign and productsign commands are failing. I have created FB10804197. It is working from our office in California. Could you please help.  regards  Prema Kumar
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to A timestamp was expected but was not found
Hi Quinn, Thank you for the support. I have tried the commands and updated the ticket. It takes more than one minute to establish the connection. Sometime the connection gets timeout as well. regards Prema Kumar
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to A timestamp was expected but was not found
Hi Quinn, I have updated in the FB10804197. traceroute command details also updated. I will give the other information soon. regards Prema Kumar
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to A timestamp was expected but was not found
Hi Quinn, We bypassed the firewall as well. Still getting the issue. Could you please try the following? traceroute from 17.179.249.1 to 103.36.149.1 and 17.179.249.1 to 103.36.149.2 regards Prema Kumar
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’22