Overview

I enrolled in the Apple Developer Program on June 4th and submitted all required identity verification documents, including my driver’s license and identity card. However, my enrollment is still showing as pending. Payment should be processed within 48 hours — but my account appears to be stuck and hasn’t progressed. To make things more complicated, there’s been a double payment situation: I initially enrolled and paid via my phone, but later accidentally withdrew from my personal computer (the status display was quite confusing). I then re-enrolled and paid a second time using a credit card. Would be great if someone could take a look.

Hey everyone, this is a difficult topic to pin down on a certain component but I don't want to assign blame anyway. I want it to go away. Looks like people started to see this somewhere at Xcode 15 but it keeps happening. Xcode 26.5 as of this writing. For Apple people reading this, I posted a bug/feedback FB20206100 including a ready-to-compile (or rather fail-to-compile) example project. The gist is: If you open a Package.swift file with Xcode and that package contain a sub-package, Xcode will insert -suppress-warnings into the build of said sub-package. This means if you add "swiftSettings: [.unsafeFlags(["-warnings-as-errors"])]" into that sub-packages Package.swift file, it wont compile. Why? Because: error: Conflicting options '-warnings-as-errors' and '-suppress-warnings' When you look into the fairly recently accepted swift evolution propsal 0443 they basically say "That's fine. Nothing to see here." or as the proposal put it: Interaction with -suppress-warnings This proposal deliberately excludes -suppress-warnings and its group-based counterpart from the new unified model. We retain the behavior of the existing -suppress-warnings flag but forbid its usage with the new options. The following rules will be applied: It is forbidden to combine -suppress-warnings with -Wwarning or -Werror. The compiler will produce an error if these options are present in the command line together. It is allowed to be combined with -no-warnings-as-errors. The current compiler behavior permits the usage of -no-warnings-as-errors or -warnings-as-errors -no-warnings-as-errors with -suppress-warnings. We will maintain this behavior. I don't care who is right or wrong here but the bottom line is that if you use sub-packages you are effectively being errored out of using "-warnings-as-errors" for (IMHO) no good reason. Could Please someone look at this and say "Yeah, that doesn't look right, let's fix this". Please Thank You Roddi P.S.: Yes, I know there have been posts before that are lamenting this. But I thought, Let's try a fresh start here.

Hello guys I am experiencing a very concerning issue with App Store Connect regarding auto-renewable subscriptions for my Tyira Companion App. Current situation: The app is live One subscription was approved All remaining subscriptions have been stuck in “In Review” for several weeks. I have already opened multiple support cases: 102865116552 102893708354 Unfortunately, I have not received any meaningful response so far. I already verified: pricing configuration, screenshots, localization, tax/banking agreements, subscription metadata, review information. Everything appears correctly configured. At this point the issue seems to be an internally stuck review state. The problem is now causing ongoing revenue loss because users cannot purchase the subscriptions in production. How can I escalate this since I'm not getting any responses.

Hi, I have been trying to update an Apple TV app. Everything goes okay and even says "Ready to test.' When I go to the BUILD area, I do not see the current build that I uploaded to submit it for Review. The app # is: 1047065428 Please help! Dan Uff

On tvOS, third-party apps cannot read number key presses from a connected keyboard or remote (except inside a text field). There is also no HDMI-CEC API. Because of this, a live-TV / IPTV app cannot let the user simply type a channel number to change channels. This excludes a large group of users, especially older people. They have used numbered channels for their whole lives — they remember that a given number is a specific channel and just want to press that number to get there. It is the simplest and most familiar way for them to use a TV. Making them navigate an on-screen grid with the Siri Remote instead is much harder and unfamiliar for them. Please give apps a way to support numeric channel entry on tvOS — for example by letting apps receive number key presses (0–9) from a connected Bluetooth keyboard/keypad without forcing a text field, or by exposing the numeric keys from the TV's own remote via HDMI-CEC. Other TV platforms already pass number keys from the remote to apps, so this works for them today. tvOS does not, which leaves these users without a basic, expected way to use their TV.

Hello, I am trying to enroll in apple developer program and I get this generic error "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time" without any reason or clarification , i tried from my PC and from my iphone device both giving me same error.

iphone 16 promax. software ios 26.6 public beta. no matter how long i take screen recoding, the video in photo will be 2 seconds. i have found this bug for a long time and hasn't been fixed

App Store Connect returns the following message when the NSExtensionPointIdentifier key in the Info.plist of a Device Activity Monitor extension contains an invalid value: ITMS-90349: Invalid Info.plist value - The value of the NSExtensionPointIdentifier key, <value>, in the Info.plist of ".../PlugIns/...appex" is invalid. To resolve this issue, set NSExtensionPointIdentifier to com.apple.deviceactivity.monitor-extension. The expected Info.plist structure for a Device Activity Monitor extension is: <plist version="1.0"> <dict> <key>NSExtension</key> <dict> <key>NSExtensionPointIdentifier</key> <string>com.apple.deviceactivity.monitor-extension</string> <key>NSExtensionPrincipalClass</key> <string>$(PRODUCT_MODULE_NAME).DeviceActivityMonitorExtension</string> </dict> </dict> </plist> After you apply this fix, build and archive your app, then re-upload to App Store Connect to confirm the error is resolved.

Hello, I'm hoping someone from App Review can help look into two submissions that have been stuck in "Waiting for Review" far beyond the normal window. Both are from the same (recently created) developer account, and both have been waiting for weeks without moving to "In Review". App 1 — EyeRest App ID: 6762698407 Submission ID: 9a1e697d-df86-4ba4-b8e9-977ceb290638 Version: 1.0.0 (build 11), iOS Submitted: 2026-05-07 — over 30 days in "Waiting for Review" App 2 — breathcare App ID: 6767147235 Submission ID: 8fedc120-b43b-48c5-8d73-c39157c75286 Version: 1.0.0 (build 6), iOS Submitted: 2026-05-19 — over 18 days in "Waiting for Review" What I have already checked / tried: Agreements, Tax, and Banking are all active (Paid + Free Applications agreements active, tax forms and banking complete). Resolution Center shows no messages from App Review for either app — I have not been asked for anything. No alerts/banners on the account or app pages. Both apps are already live on Google Play, so the builds are functional. I would prefer NOT to withdraw and resubmit, since that would send them to the back of the queue and likely won't address whatever is holding them. Could someone please check why these two submissions are not progressing? Thank you.

Hi everyone, I'm hoping someone here has experienced this and can point me in the right direction. I submitted my first app, Homeowners Checklist, for review and on May 21 the status changed to "Ready for Distribution." It has now been over two weeks and the status has never changed to "Ready for Sale" and the app has not appeared on the App Store. Here is my current setup: App Store Version Release is set to "Automatically release this version" There is no scheduled release date set All agreements in Agreements, Tax, and Banking show as Active I have not received any emails from Apple indicating there is an issue This is my first app on a new developer account I have contacted Apple Support multiple times via email and phone with no resolution. My case has been open since May 21 with no clear answer. Has anyone experienced this with their first app? Is there something I might be missing, or is this a known delay for new developer accounts? Any advice on who to contact or how to get this resolved would be greatly appreciated. Case ID for reference: 102900108706 Thank you

Hi everyone, I am running into a critical issue while trying to set up TestFlight / manage builds via the App Store Connect API. The system constantly throws an HTTP 422 error with the following payload: { "errors" : [ { "id" : "d7e4e2fa-8c25-4a37-9695-f75da935b8aa", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Important context about my setup: This is a brand new Apple Developer account. This app has never had a successful build uploaded or processed before. All agreements, banking, and tax contracts under the "Business" section are active and signed. There are no pending actions on my dashboard. It seems like the system is looking for a "Beta Contract" that should be automatically generated or triggered, but since this is the first deployment on a new account, it’s completely stuck. Has anyone experienced this specific issue with a new account? Is there any way to manually trigger the creation of this Beta contract, or is escalating this to Apple Engineering the only solution? Any advice would be greatly appreciated!

Released a new version of my app, which is currently live at version 1.1 on the App Store. When testing directly from the app store, the app's button says "Update". When I tap Update, it will do the usual loading, and for 0.5 seconds finish but then go back to the "Update button" again, and my latest app version never gets installed, it sticks to 1.0. I've tried the following: Stopped testing on TestFlight Reset All Settings on iPhone Signed out and signed into the App Store with a different Apple Account Reached out to Apple Customer Support (no response) Deleted and re-installed the app Any help is appreciated!

So for last two years ive been dealing with unwanted unauthorized access to my data having zero clue what was the reasoning it. I need help to fix this please. I deal with random people "linking" up to my "whatever syncing or streamin" I never signed up for anything this and lost everything in my life over this. I finally found out the root (which is this program apple offers) and it's being used maliciously 100%. please help

I would like to implement a focus-based Menu-Bar command in my SwiftUI iPadOS app, or react to key command while certain elements are focused. Traditionally, this requires using @FocusedValue and focusable() and focused, however, it appears that setting a @FocusState on macOS will work, but setting a @FocusState on iPadOS will never work. How can this API work and support MenuBar commands and keyboard inputs? It kind of has an accessibility impact as well. Not all users are going to know, or want to turn on "full keyboard control" for basic interactions. Here's a small sample that doesn't appear to focus on iPadOS: struct FocusableTestView: View { @FocusState private var isRectFocused: Bool var body: some View { VStack { // This text field should focus the custom input when pressing return: TextField("Enter text", text: .constant("")) .textFieldStyle(.roundedBorder) .onSubmit { isRectFocused = true } .onKeyPress(.return) { isRectFocused = true return .handled } // This custom "input" should focus itself when tapped: Rectangle() .fill(isRectFocused ? Color.accentColor : Color.gray.opacity(0.3)) .frame(width: 100, height: 100) .overlay( Text(isRectFocused ? "Focused" : "Tap me") ) .focusable(true) .focused($isRectFocused) .onTapGesture { isRectFocused = true print("Focused rectangle") } // The focus should be able to be controlled externally: Button("Toggle Focus") { isRectFocused.toggle() } .buttonStyle(.bordered) } .frame(maxWidth: .infinity, maxHeight: .infinity, alignment: .center) } }

I can't send text messages from my MacBook Air (Tahoe 26.6) to Android phones. This just happened this week, after successfully being able to send them since purchasing this laptop (2023 - M2 chip). I've checked the settings to make sure that my iPhone and my laptop are signed into iCloud (they are), and that I have message forwarding set up on my iPhone. I can get texts on my laptop from Android users, but I can't reply - the texts fail every time. I've searched the community for an answer, and have tried previously suggested fixes to no avail. Any thoughts?

Hi everyone, Apple took $79 from my bank account last week because I wanted to sign up to sell my app on the store. In my account, it says you need to complete your purchase, but the money has been charged in my account, and I have no access to any developer account. I have sent two emails to Apple support with no reply. Does anyone know how to get a refund or how to fix this?

Hello Apple Developer Community, I’m Samriddhi, a student at Hult International Business School studying Business Analytics and Design. I’m interested in exploring a potential collaboration with Apple around student life, creativity, productivity, design, and how Apple products support learning and creative work. I couldn’t find a direct official email for collaboration requests, so I’m posting here to ask if anyone can guide me toward the right Apple team, contact channel, or partnership process. I would be happy to share my audience details, content ideas, and previous work privately with the appropriate team. Thank you for your help.

About 90% of the time I attempt to upload my app build to App Store Connect 'Internal Testing Only', it gets stuck on either "Sending SPI Analysis to App Store Connect" or "Waiting for App Store Connect SPI Analysis Response". The only solution I've seen is to sign in and out of my dev account in Xcode and close the app - and keep repeating this process until it works again. Sometimes it takes one, sometimes it still won't work after doing this 10 times. I learned that I can export the IPA and upload via Transporter which I have been doing recently. But this is an extremely annoying problem that I do not understand why it continues to happen every session, and I have seen barely any other forums anywhere with this same issue. Can anyone help?

Hello everyone, our application version update (version 3.1.1) has been waiting for review for a long time without any progress or response to the support issues we raised. Application Apple ID: 6752632655 First submission date: April 17, 2026 Last resubmission date: May 28, 2026 Current status: awaiting review (never moved to 'under review') We have raised the issue with the developer support department, but have not received a response yet. We are not requesting special treatment, we are just requesting a status check or any indication of any obstacles. If anyone from App Review sees this, we would greatly appreciate it. If other developers see similar waiting this week, it would be helpful to know that this is a backlog rather than a flag on our account. Thank you.

Hi, I have the NFC &SE entitlement but still not able to read a pass from the apple wallet on another iphone. The logs show that the NFCVASReader session is initialised and the readerSessionDidBecomeActive — session is live, waiting for pass tap, but nothing is read. The pass is nfc enabled with correct encryption key. It feels like I am still missing some kind of entitlement to read VAS from passes - could anyone advise please?