I saw the descriptions in tvOS 15.4 Release Notes, the bug might be fixed on Xcode13.3 and latest OSs.

Yes! I think I am looking for StoreKitError. Thank you!

Thank you for the comment. It seems strange to write test code that takes into account the delay of StoreKitTest, so it looks better to wait each Transaction.updates by XCTWaiter, as in testcase1. What do you think about it?

I've checked willAutoRenew became false in my sandbox(testflight) environement. The answer saved me a lot of time! Thank you!

Although I encountered the removeObjectIdenticalTo:]: unrecognized selector sent to instance xxx error where I tried calling NSTreeController.move(_:to:), the @Kela replies solved my problem! (Thank you very much, the answer saved my lot of time!)

I tested Synchronizing Documents in the iCloud Environment with iOS17.5.1 device, then it succeeded. The containerRootURL.startAccessingSecurityScopedResource is true, but the both errors are still presented. I will investigate what the difference between success one and failure one. (It might be only timing when I created the iCloud container, because iOS17.5.1 provides significant bug fix updates for iCloud and it might affect with this problem)

My project's containerRootURL.startAccessingSecurityScopedResource is false 🤯

Re-creating iCloud container with other containerID doesn't solve the problem.

Thank you for the reply @_lilpit ! I've already reported the issue few months ago, but no response...😢 Cloud you teach me how do you detect the XPC crash? I am currently asking Apple a question using a TSI (Technical Support Incident) ticket. If the customer support engineer is unable to answer, the ticket is usually passed on to a framework engineer. If that happens, there might be some progress !

I've just found an easy way to detect crashes (or rather, force a display update)! Thank you!

I got response to my feedback report. “Hello! Thank you for your Family Controls Framework feedback and providing a code snippet! We are currently investigating this report and may be in touch soon for additional information.” It seems they are investigating my report !

@Engineer I've reported this twice. FB14067691 and FB15260613