“apple pencil charging”

I am writing to share my frustration regarding the app review process for my application. My current submission has been stuck in Waiting for Review for nearly 7 weeks, starting from February 5th. Although I have attempted to cancel and resubmit periodically, there were significant gaps of 10 and 21 days between submissions where no action was taken. Currently, I am stuck again. The situation is critical for the following reasons: Critical Bug: The update includes a necessary fix for an In-App Purchase bug that is preventing users from accessing paid features. No Communication: I have sent four inquiries regarding this delay. I received only one generic response asking me to wait, and my subsequent follow-ups have been completely ignored. Expedited Review Request: My requests for an Expedited Review have also gone unanswered. Apple’s standard review time is typically 24-48 hours, but my experience is far from that. I am not asking for special treatment; I am asking for basic transparency regarding wh

I signed up for an Apple Developer Program last week. I paid the $99 fee for the account. However, the account still shows pending and the payment alert is still active on the dashboard. I checked my card statement and I do see that the $99 charge hit my account. I believe I paid for the developer account on the morning of the 18th, it's now the 22nd. Any suggestions?

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 Mo

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 correction of an already

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 correction of an already

Hello, My Apple Developer Program subscription is active in Apple subscriptions and valid until March 19, 2027, but my developer account is still not activated and I have not received the confirmation email. The purchase was completed through the Apple Developer app on my wife’s iPhone, but the enrollment was for my own Apple Account. In the app, I see the message: “You’ll receive an email soon.” Has anyone had the same issue? How was it resolved? Thank you.

When I first uploaded my game, they rejected it after 10 days. Then uploaded it after adding a new feature, but even after one month, there are no updates from them. So I rejected it myself and uploaded a new build with new features. And that was on Feb 6, 2026. Now it's more than 1.5 months, and no updates. When I contact them, they say they ESCALATED the review 3 times, but still have no update from the app review. But I can see many other apps getting approved after Feb 6 in Reddit posts. So what makes my game wait in the queue for more than 1.5 months? Also, why can't Apple employees say the proper reason not to start the review? They are charging 100 per year and not even reviewing the one game I uploaded.

I enrolled in the Apple Developer Program as an Individual on March 16, 2026 (Team ID: CAZ8X23YWW). I've been trying to notarize a macOS Electron desktop app ever since. Every submission is immediately rejected with: Status code: 7000 Message: Team is not yet configured for notarization What I've done: Accepted all agreements on developer.apple.com Accepted all agreements on App Store Connect Created a Developer ID Application certificate (G2 Sub-CA) App is properly signed with hardened runtime Submitted a support ticket under Distribution > Other Distribution Questions on March 18 — no response after 4 days

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

I’m currently developing an iOS app that relies heavily on location details. I'm using MapKit and MKMapItem as my primary data source, which works perfectly for standard metadata. However, I’ve hit a roadblock: I want to display opening hours inline within my location details, but it seems Apple doesn't expose a public API or property for this in MKMapItem (even though the data is clearly visible in the native Apple Maps app). Since I'm building this as an indie developer/startup, the Google Places API is unfortunately too expensive for my current budget. ⁠Is there any legitimate, native way to get opening hours from Apple that I might have missed? ⁠If not, what are your best practices or recommended indie-friendly alternatives (e.g., Yelp Fusion API, OpenStreetMap, Foursquare)? Any tips on how to handle this elegantly and cost-efficiently would be highly appreciated! Thanks in advance.