Hello @eskimo , thank you for the last answer! Could we please continue this discussion if you have some time? The results of this discussion are still not clear for me, unfortunately. I noticed in my altool that it throws "altool has been deprecated for notarization and starting in late 2023 will no lo\U2026". I suppose that this is the main reason of why guys want to use notarytool instead of the altool. So, the last thing you said is: "Note that the two commands you’re using are not equivalent. notarytool targets the notary service, but altool --upload-app targets App Store Connect." Could you please give us a hint, what can we do to make the notarytool targets App Store Connect and behaves the same as altool (altool was uploading .ipa directly to the testflight)? Unfortunately, I have no opportunity to upload builds with help of XCode, since I use a non-common approach of making iOS builds. Thank you!

Hello again @eskimo After some investigation I found out that the next message: "Notarization":{"Message":"altool has been deprecated for notarization and starting in late 2023 will no longer be supported by the Apple notary service. You should start using notarytool to notarize your software.","Status":"DEPRECATED"} is just a warning about notarization that is related only to macOS software (https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution). But the warning doesn't mean that the altool itself will be deprecated. It seems like altool is still valid for uploading .ipa files to TestFlight and notarytool is needed for macOS .pkg files. Please correct me if I'm wrong. Thank you!