“Account Locked”

Can you file a bug on this and upload the full spindump there? I opened one last week. Case-ID: 18860388 ...this is almost CERTAINLY caused by your ES client. Yes. The question here isn't what revisiond is doing, it's who revisiond is waiting on. Some other thread locked that lock and is now stuck, which is the real issue you need to sort out. It definitely revisiond (well, APFS), that's holding the lock. There are dozens of threads where the shared lock points at revisiond [426] thread 0xc0616d), both for reading and writing. *940 apfs_vnop_getattr + 312 (apfs + 604336) [0xfffffe000beacff0] *940 IORWLockRead + 144 (kernel.release.t6000 + 496568) [0xfffffe00088e53b8] *940 ??? (kernel.release.t6000 + 497548) [0xfffffe00088e578c] *940 ??? (kernel.release.t6000 + 619452) [0xfffffe00089033bc] *940 ??? (kernel.release.t6000 + 624472) [0xfffffe0008904758] (suspended, blocked by krwlock for reading owned by revisiond [426] thread 0xc0616d) *940 apfs_vnop_read + 708 (apfs + 555972)

After 7 hours, successfully managed to get my first deployment on the watch. Definitely not something you expect from apple, in fact I cussed them out the whole way through. But here's what I did Mostly followed entouss's guide and most advice is reiterated from him + some of my experiences Before you do anything, make sure Apple Watch is fully charged (this WILL take a long time) It has a passcode You might get the bright idea to remove the passcode and put it on charger to prevent lock. Keep it on. Pre-pair Make sure you're on a 2.4 ghz network (mobile hotspot or create guest network on router) Connect all devices to that network Shutdown all devices and start them up 1 by 1 to start from a clean slate Get it to show up in Xcode devices If your apple watch is already in the xcode device list, DO NOT unpair it as it may not show back up again without large hassle WATCH for trust this device messages on your apple watch. If you accedentally press no, or press the crown while the dialog is on, you gon

Hi @tomatomato, @jarrodlombardo-eventbase, @raphaelkohncr, Thanks for your continued patience. Before I begin, the answer below applies to current regional requirements as of the iOS 26.4 release, and should also be used as guidance for any upcoming regional regulations. You wrote: 1. What's the return value of IsEligibleForAgeFeatures for a Brazilian user who has NOT touched the age range feature at all, thus hasn't picked one of the three options? The intended usage of isEligibleForAgeFeatures is to determine whether associated laws or regulations may apply to your app based on the person's region and account settings. If your app is eligible for age-gated features and needs to support age assurance for the current user, the property returns true; otherwise, it returns false. It's a simple boolean value—if you require more granularity for the specific regulatory requirements, use requiredRegulatoryFeatures as well. Next, you wrote: 2. How can we test these cases? From the updated sandbox doc, there

We're experiencing a deadlock on certains systems when our software is installed, which is causing side effects in our process (and likely others) such as blocked queues and increased memory usage. According to the spindump, revisiond appears to be holding an exclusive lock within the kernel. Can you file a bug on this and upload the full spindump there? That's the easiest way to transfer large data files and I may eventually want a sysdiagnose. Having said that... Our agent uses Endpoint Security Framework to monitor events, and provide anti-tamper functionality for installed components and processes. While several EndpointSecurity calls appear in the spindump stack traces, we don't have any evidence that any calls from revisiond were blocked. ...this is almost CERTAINLY caused by your ES client. What we'd really like to to understand what that lock is (appears to be decompressing an object on an APFS volume), what revisiond and APFS are doing with it, and what might cause it to deadlock. Y

Hi @jarrodlombardo-eventbase, You wrote: How can we determine if the user is eligible for the TX versus other state requirements? Before I begin, the answer below applies to current regional requirements as of the iOS 26.4 release, and should also be used as guidance for any upcoming regional regulations. The Declared Age Range framework provides two ways of determining eligibility and requirements based on the person using your app: isEligibleForAgeFeatures requiredRegulatoryFeatures Use isEligibleForAgeFeatures to determine whether associated laws or regulations may apply to your app based on the person's region and account settings. Use requiredRegulatoryFeatures, in addition to isEligibleForAgeFeatures, to determine which regulatory features apply to your app based on the person's region and account settings. Note: Regulatory features added in upcoming regulations (for example, after iOS 26.4) may or may not be included in the existing set of RegulatoryFeature types in iOS 26.4, so requi