“We are unable to process your request”

Hi everyone, I’m the developer of one sec, an app used by a large number of users globally to reduce time spent on social media and to build healthier digital habits. Because of this, we rely heavily on Apple’s Screen Time / DeviceActivity / FamilyControls, ManagedSettings APIs – and unfortunately, we’re seeing increasingly severe issues in production that directly impact hundreds of thousands of real iOS users. During the past years, we have been busy filing dozens of feedback requests for different Screen Time issues – and there has been no response from Apple at all. Developer Relations might be able to confirm that the bugs are present and that they ended up with the right team – but they are never addressed, neither are workarounds provided. Instead, the situation gets worse and worse. iOS 26 introduced a series of heavy regressions (which have been reported via Apple’s official bug report tool Feedback Assistant on iOS 26 beta 1 in June 2025 – and have not been addressed 10 Months later). This

Hello, I have a critical issue regarding the Family Controls (Distribution) entitlement. My app FocusPact was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a Bundle identifier prefix mismatch error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correct

Hello, I have a critical issue regarding the Family Controls (Distribution) entitlement. My app FocusPact was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a Bundle identifier prefix mismatch error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correct

Hi all, Has anyone else experience review bombs and how effective was Apple at remedying it? In my case there is zero guidance and zero substantive insight by Developer support how I can effectively remedy a dishonest/bad-faith review attack on my application by a competitor. What are the criteria or guidelines for assessing an ‘attack’ under Apple Media Services Terms of Service section M? And the same for ‘bad-faith‘ and ‘dishonest‘ reviews? In my case I had an encounter on Reddit with somebody threatening to review bomb me, explaining to me how they knew how to bypass the Apple review system, and critiquing my app with specific comments. On that same day I received a 1 star review including exactly the same ‘critiques‘ that the Redditor gave me, written in German instead of English. Who here wants to guess the nationality of the Redditor? Before I received the review I had already notified Apple of the fact that I had this interaction and I was expecting a review bomb. I explained the explicit intention an

Since 26.4 beta 3 I've been having errors after a few hours of using Claude Agent. I get an error stating that I am not authed. If I go into Xcode settings, it still shows I am signed into Claude Agent. I have click sign out and then go through the whole auth process again to start using the agent again. This is on two separate computers. Is there anything I can do to stop this behaviour and stay logged in for longer? It worked fine in 26.3.

Hello, I’m experiencing a performance issue: I poured some tea, but it’s taking too long to cool down, so I can’t start drinking it. I tried moving the cup to the balcony, but the latency is still high. Could you please advise how to speed up the process?