apple pencil charging

Hot take: Apple needs to ditch the '90% of apps reviewed in 48 hours' metric and just give us a worst-case ETA. It’s basic UX psychology: underpromise and overdeliver. If you tell me it takes a week and I get approved in two days? I’m stoked. But right now, the second that 48-hour mark hits, I’m stuck spamming F5 and doom-scrolling dev forums, looking for clues and convinced I’ve fallen into that cursed 10% with bad RNG. The 'Waiting for Review' status is a total black box—it tells you nothing. I saw some poor soul on Reddit who’s been in review limbo for three months... makes waiting a couple of weeks feel like a nothingburger. Honestly, just give us a hard upper limit. It’s way better for our sanity and actually lets us plan our roadmap around the worst-case scenario.

Do you have access to the latest source code for your project? That's really the key question here. I agree with the poster above — when I've done development in the past, the app owner has their own Apple Developer account and invites the developer to join their team. The app should be submitted to App Review through the owner's account, not the developer's. A couple of other things to be aware of: if the annual Developer Program fee isn't paid and the account lapses, Apple will remove your app from the store. Once that happens, it's much harder to recover, so time is important here. Also, check any contracts you have with the development company. You may have rights to the source code, which could matter if the company's assets are being handled through bankruptcy proceedings. Without the source code, you'd essentially be starting over from scratch. The good news is that if you do manage to get the code and set up your own developer account, Apple has an app transfer process in Ap

I've been in Waiting for Review since Jan 27 with no movement. We missed our launch date as well. Originally, we submitted on Jan 23, mistakenly assumed there was an issue because our app didn't move, and resubmitted on Jan 27. In hindsight, it likely lost 4 additional days. After submitting 3 requests to Apple Support, just to confirm our app was queued, they got back to us saying it was and that no additional action was required on our side. We're burning a ton of cash daily on back-end services that are running so Apple's reviewers can test all features, and our devs are sidelined until we get word on Apple's decision (first-time app submission). We anticipated the real challenges would begin once our app launched, and never thought they would start with Apple's review process. For what it's worth, it's the lack of communication and clarity from Apple that's been frustrating. Honestly, if they simply said we're backlogged and actively working to clear the queue,

Hi there, You're on the right track in wanting to retain full control of your Apple Developer account while working with a freelancer. The best and most modern approach is to add the developer to your App Store Connect account with the Developer role. This allows them to access the necessary signing tools in Xcode without needing your personal credentials, and they can submit the app directly through App Store Connect. Sharing certificates and private keys (as your developer suggests) can be risky and is no longer considered best practice. Instead, you should handle signing through Xcode and App Store Connect, which ensures both security and control. This way, your app remains under your Apple Developer account, and you retain long-term control while allowing the developer to work without compromising security. Hope that helps! -Dean Reyburn, reyburnengineering.com iOS/MacOS app developer

I have this issue too. Payment made on iPhone. I can see the subscription in my subs. However, when I log in, the status says pending and there's a link to continue through to payment. I've emailed Apple Support but so far no reply (Case: 102821244027) @Apple Developer Support

My team has also encountered a similar situation. In mid-January, the build (App ID: 1552207792) was submitted for review and remained in the Waiting for Review state for several days. The status did not change, so we tried resubmitting the build, but that did not help. A week later, we resubmitted it again after accepting the new Terms of Use in App Store Connect, thinking that might have been the cause of the delay. Currently, the app has been stuck in Waiting for Review since February 4th — it has now been 10 days. A request for an expedited review and contacting Apple have not had any impact on the situation.

Hello, I have the same issue. I was charged $98.99 on Feb 9, received the automated confirmation, and haven't received any follow-up since. I contacted Apple Support after two days, but they haven't responded. I'm worried my case is stalled, and I probably won't get a refund. Not sure what to do either.

I had the same problem; what I did was log out (and yeah, trying to log out properly with Codex is a big pain—you need to remove the config files). Then follow the instructions, and after I logged in the spinner ran on the GUI. I fired up Codex in Terminal, waited a moment, and closed the spinner UI. It told me it failed, then quit Xcode and Codex, and it should then let you continue as if nothing went wrong. to install the CLi version: https://developers.openai.com/codex/cli Of course, yesterday after I installed macOS 13.3, Xcode froze on startup, telling me it was trying to recover a document that was not saved correctly. I wiped Xcode and ~/Library/Developer, rebooted, and installed Xcode 26.3 RC; the problem was still there (?). Installing Xcode 26.2 made the problem go away. The issue must be with Codex. Uninstalling Codex does not help either—it keeps hanging on startup—so I wiped Codex config files in ~/Library. Xcode still hung, but I could click on the menu and get a response; tapping on the “triang

If you've enabled MusicKit in the Apple Developer Portal but your build fails with Provisioning profile doesn't include the entitlement, here is the fix: Do NOT add the entitlement to app.json. Apple now treats MusicKit as a Runtime Service, meaning it is checked on Apple's servers when the app runs, not stamped into the .mobileprovision file at build time.

Update: I received a response from Apple Developer Support. They suggested re-submitting the enrollment using the Apple Developer app to resolve the payment issue, since alternative payment options are only available through the app. However, this would likely result in a second charge to my credit card, and the app does not even show an option for me to re-enroll or restart the process. I don’t believe it is an optimal solution to require another payment to fix this issue. They asked me to confirm whether I want to proceed with re-enrollment via the app. I will share another update once I have more information.