“Account Locked”

Thank you for sharing your post. I understand that it can be frustrating, especially when the job is impacting your daily routine. I am eager to assist you in any way I can. I have a potential idea, but I would like to request a bug filing for further investigation. Typically, authentication tokens expire after a few hours. In a stable build, Xcode silently uses a “refresh token” to obtain a new session in the background. Consequently, the system may be terminating your session when the initial token expires. This is an issue that requires immediate attention. However, I am only speculating about the cause. Given that this issue is occurring across two separate computers and began specifically in beta 3, it is highly probable that the problem lies within the beta itself rather than a misconfiguration on your end. Instead of simply signing out and signing back in, I recommend completely deleting the integration from Xcode. Navigate to Xcode > Settings > Accounts (or the specific Claude Agent set

Let me start by saying two slightly contradictory things: It's very likely that there is an APFS bug here, so if you haven't already, please file a bug on this and post the bug number back here. It's ALSO very likely that your ES client (possibly both ES clients) are required to actually experience this bug, and you should address it as well. Next, I think I want to be clear that some of what I'm saying is a bit of an educated guess. A big part of the problem here is that the data we're looking at is being collected LONG (2+ days) after the problem itself actually occurred, which means we don't REALLY know EXACTLY what happened. That doesn't invalidate what I'm describing above, but I do think it's important to have some awareness of the limitation of the data at hand and that, most importantly, new data could totally change our understanding of the overall state of things. Getting into the details: But here, I don't see such things. When EndpointSecurityEventManager is on the spindump, it's only because they

Thank you for your post. The App Store team does not monitor the forums, and I believe you set your app as “Made for Kids” for the first time when you deployed the app. Since your app is already live, the “Made for Kids” flag and the “Kids” category are often locked to prevent developers from changing an app’s target audience without parental consent. This will be a significant privacy issue as you can see. To resolve a locked metadata field like that, you need to contact App Store Connect Support, not App Review. Visit the Apple Developer Contact Us page. The representative can file an internal ticket directly to the App Store Connect engineering team to manually unstick the metadata field on your account if appropriate. Now, depending on your app and the people affected by that change, the engineering team will decide whether to make that change. I’m not in that team now I know their process. Once App Store Connect Support unlocks the field and you successfully uncheck “Made for K

Hi, We are also affected by this TestFlight issue. The build is visible for internal testing, but when testers tap Install, TestFlight says: “The requested app is not available or doesn't exist.” We already checked the usual things and even tried creating a brand new app record, but the exact same problem still happens. It looks like many developers have run into this before. If anyone has a confirmed solution, please help share it. Was it: an Apple/TestFlight backend issue? an account/app distribution state issue? something Apple Support had to manually fix? Any real experience would be greatly appreciated.

Lots of interesting things to check in your answer, thanks ! That's said, I have a last question (on my side) regarding Endpoint Security. In the past, when I had to investigate deadlocks where ES was involved, we 100% of the time saw symbols like EndpointSecurityEventManager::es_something and/or EndpointSecurityEventManager::sendSomething, and something which show that they are waiting for an answer (for auth events, but I guess it can happen with notify events when the queue is full, and ES is not willing to drop the new events - I think someone from ES team explained to us some years ago that ES can try to slow down entering events to make a chance of the client to empty a bit the queue…), before being killed by ES kext itself. But here, I don't see such things. When EndpointSecurityEventManager is on the appear in the spindump, it's only because they are blocked, like anyone else, on one of these 2 lock. There is known typical scenario where ES can result in such double lock interlocking

Hi, I read your post and it sounds like an incredibly tough situation. I’ve been through a Pending Termination Notice myself, so I truly understand how stressful this can be. I’d like to share my experience just in case it might be of some help. At this stage, it might be more effective to focus less on defending the anti-virus app’s innovation and more on protecting your developer account and your livelihood. In my own case, focusing on a few specific points in my appeal seemed to make a difference: Clarify your intent: Since the app was flagged as malicious, you might want to clearly explain that you had absolutely no intention of misleading users. While your personal situation (such as losing your source of income) is completely understandable, Apple’s review process is guideline-driven, so I think it might be more effective to keep the tone as professional as possible. Write a concrete preventative measure: I mentioned this in another thread recently, but I believe including a clear preventative