“Account Locked”

i have the same issue, i have a claude account paid, with xcode 26.3 but im having infinite loading after finishing the SSO. The infinite loop appears in xcode

I want to share all the content of a CloudKit database at once between different iCloud accounts. For example, to manage products storage between users. Once the database has been shared or an invitation has been accepted, any additions/modifications/deletions to storage or products must be shared between all users without additional sharing. To be short after the first sharing, everything must be shared without additional new sharing. I think I can't do this in SwiftData (would be the best solution for me as all the current app is based on SwiftDaa) and that I need to use move to CoreData. Is that correct? Or does a mixed solution may be possible (ie .storage with SWiftData and sharing with CoreData)? It seems that “Zone Wide Sharing” could be the solution? But I can't find a sufficiently comprehensive example and I wasn't able to make something working. Ultimately, I realize that this is not a very common use case. With the ZoneWide Sharing does it means that we must do a affectedStores or assign(_

Hooboy, knowing if we've seen it on Intel machines will take some digging. The M1 Studios we have are 2022. Our ScriptingBridge code was added in June 2023. The first internal mention of errOSAInternalTableOverflow is December 2023. The M1 Studios weren't put into production until March 2024 (that's how slow our IT department moves). By this timeline, it appears we were seeing errOSAInternalTableOverflow on Intel. As for the actual crash described in this thread and bug, that I'm not sure about. I'm assuming that getting errOSAInternalTableOverflow and this crash are caused by the same underlying bug. No PowerPC Macs have been in use during my tenure at this job. Naturally, I figured it would be a very long time until a possible Apple fix would reach our production machines. Time to diagnose + time to fix & test + time to release + time for our IT department to OK the user of that version of macOS. I just might be retired by then. Moving the bulk of the job code to a separate helper app will be fairly sub

We're seeing this same behavior in our enterprise environment and have been able to isolate it to a specific mechanism in SecurityAgent's launch sequence. Environment: macOS Tahoe 26.3 MDM-managed Macs (Jamf Pro) Non-admin user accounts Admin By Request 5.2.0 (authorization plugin: AbrAuth) What we found: We built a lightweight detection tool using NSWorkspace activation notifications and a CGEvent tap to catch the moment focus shifts, then captured unified logs (±5 seconds around each event) filtered to the authorization subsystem, process lifecycle, and WindowServer. The logs show a consistent chain: A LaunchDaemon (mdmclient, JamfDaemon, or AssetSonar in our case) requests system.privilege.admin authd evaluates the right and walks the authorization plugin chain SecurityAgent spawns to host the plugin evaluation (AbrAuth:invoke) SecurityAgent registers with WindowServer (SLSSetFrontProcessWithInfo with window=0) Focus transfers to SecurityAgent — despite no window being displayed The authorization

I’m experiencing a very similar situation. Multiple iOS app updates (already live apps) have been in “Waiting for Review” since February 6–11 (4–5 weeks now). All agreements are active, builds are properly attached, and there are no compliance or metadata warnings in App Store Connect. One of the submissions was even marked for expedited review about a week ago after contacting App Review Support, but the status has still not changed from “Waiting for Review.” This appears to be more than a normal backlog. It may indicate a queue or account-level issue. Would appreciate any updates if anyone sees movement on their submissions.

I’m experiencing a very similar situation. Multiple iOS app updates (already live apps) have been in “Waiting for Review” since February 6–11 (4–5 weeks now). All agreements are active, builds are properly attached, and there are no compliance or metadata warnings in App Store Connect. One of the submissions was even marked for expedited review about a week ago after contacting App Review Support, but the status has still not changed from “Waiting for Review.” This appears to be more than a normal backlog. It may indicate a queue or account-level issue. Would appreciate any updates if anyone sees movement on their submissions.

I’m experiencing a very similar situation. Multiple iOS app updates (already live apps) have been in “Waiting for Review” since February 6–11 (4–5 weeks now). All agreements are active, builds are properly attached, and there are no compliance or metadata warnings in App Store Connect. One of the submissions was even marked for expedited review about a week ago after contacting App Review Support, but the status has still not changed from “Waiting for Review.” This appears to be more than a normal backlog. It may indicate a queue or account-level issue. Would appreciate any updates if anyone sees movement on their submissions.