Before this, the OS26 beta version, for the online package, after payment, it was also impossible to finish the transaction, but later Apple officially fixed this problem, and now TestFlight has this problem again, is it that Apple engineers have put the wrong branch back together？

This seems to be a bug in the Apple system, under TestFlight, after payment, the order cannot be finished, resulting in the inability to purchase again. This usually happens on OS26 systems. iOS26 and below do not have this problem.

苹果服务器问题，但目前 苹果也没出公告，也没给个修复时间。

https://developer.apple.com/support/third-party-SDK-requirements/ apple says that "Xcode will combine the privacy manifests across all the third-party SDKs used by your app into a single", But actually, xcode doesn't do this, and you may need to wait for xcode to update?

After March 13th, we uploaded IPA packages without a privacy manifest and we still haven't received a warning email from AppStore Connect. So even if we add a privacy manifest, we still can't verify that the privacy manifest we've added in the IPA is correct. Has anyone encountered this situation, is Apple grayscale releasing this feature?

From Apple Thank you for your feedback. These is a known issue that has been addressed. Can you please verify? If you are still experiencing this issue, please provide more information about the incidents. If the issue is resolved, you can close this feedback by selecting “Close Feedback” via the Actions button found above. If we don’t hear from you in the next two weeks, we’ll assume the issue is resolved or not reproducible and will consider this issue closed. After this time, you can create a new Feedback report if the issue remains. Thank you.

chmod 755 your plist file

Guys,It should be a problem with Apple's system. Apple released StoreKit2, which may affect the current payment system. Wait for Apple to fix this problem.

I also encountered this problem, maybe it`s a beta system problem.Egg pain

Maybe it is a bug in Apple's sandbox environment and hope it will be fixed soon. The production environment has been verified, and there is no such problem.

nobody