“Account Locked”

% sudo defaults write /Library/Preferences/com.apple.loginwindow screenUnlockMode -int 2, I have got the solution that with SFAuthorisation how to invoke the Lock Screen UI , this also we need to set. here he the link that recommended solution from the DTS engineer. https://developer.apple.com/forums/thread/739038

I want to be clear about where things stand. My developer account renewal was processed and payment of £79 cleared my bank on 12 March. I have a bank statement confirming this. The account was therefore active and paid in full — I am not in arrears. Despite this, my app has been removed from App Store Connect and I am now being asked to pay again. This is unacceptable. I will not pay twice for the same membership period. I have two requests: Confirm receipt of the 12 March payment against my account (Team ID: AW699Z7G8H) and restore my app listing immediately. If Apple cannot locate the payment, I will provide my bank statement as proof of transaction and expect the app to be restored upon receipt. If neither of these is actioned, I will have no choice but to dispute the original charge with my bank and submit a formal complaint. I would prefer to resolve this without escalation — but four months of unresolved support and case 102841743378 still open leaves me with limited options.

Hello, Thanks for your response and for pointing me to TN3186. I have carefully followed the troubleshooting steps, but the issue still persists. Below is a detailed summary of the current situation. Configuration status: The auto-renewable subscription is fully created in App Store Connect Product ID: sylvoy_sylvoy_premium_v2_monthly Status: “Ready to Submit” Pricing is configured and available across regions The subscription is correctly added to the app version under “In-App Purchases and Subscriptions” StoreKit is properly implemented and getSubscriptions is called with the correct product ID Testing performed: Tested on a physical device (not simulator) Logged in with a Sandbox Apple ID Logged out and re-authenticated the App Store account Reinstalled the app multiple times Waited for propagation delays (over 24 hours) Verified that no StoreKit errors are returned (only an empty product array) Confirmed that bundle ID and product ID match exactly Current behavior: getSubscriptions() always retur

Sending an email with your situation well documented generally helps. After logging in with your account, clicking this link should lead you to Apple's developer support about program enrollment: https://developer.apple.com/contact/topic/SC1101/subtopic/30006/solution/select Good luck!

I mistakenly created that FB ticket on the wrong account. Here is the correct ID: FB22345323

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