Just as an update, the notary service that Apple hosts with AWS is still being targeted by an incorrectly configured SotoAWS client in notary tool. Current success rates are around 14%, over the past 25TB of uploads. The relentless looper upload-until-it-works script runs all day and all night to get these games notarized. It appears that Apple knows this is an issue but refuses to fix it, even after the developer of the open source library they are using pointed out the change they need to make in the code for notarytool. I suppose the AWS bill just isn't enough to make anyone at Apple do anything. Bummer!!!!!

I am glad to hear you say to have worked with people who have been able to successfully upload large files. Can you share any of the studio or developers so that I can contact them and ask for a reference? In your previous posts on threads about notaryservice's failures, there are replies from developers reporting a failure rate above 50% on a tiny 700MB upload. I am surprised Apple is not more concerned about this situation. My own experience, and the experience I have heard from the developer community stands out as overwhelmingly negative. I inquired with two Unity developer groups on Discord. I did not find a single developer who has had a consistently successful experience with uploading large files to notaryservice. I did find other developers who indicated that notarization is what prevented them from releasing a Mac OS X build. I wish I had known that the notary service was so poor at handling large file uploads before we committed to a Mac OS X port of the project. I think if I had known that uploads would take 48 hours of work per update, we would have just explained the weaknesses in the Apple infrastructure to our Kickstarter backers and begged for forgiveness. One of the developers did provide a nice bash script that wraps notaryservice and loops until it is successful. Today I was able to notarize a 6.05GB file but it took uploading 110GB of data to the S3 bucket. This does give me some hope that I can brute force my way past the issue for the 17GB file. I will start it and let it run continuously for a few days to see if I can force my way past defects in the uploader. Every time I start an upload, with the loop script or manually, it prints something like this: Conducting pre-submission checks for PROJECT.zip and initiating connection to the Apple notary service... Submission ID received id: f8476ccd-xxxx-yyyy-zzzz-21ae7d77581a