Overview

Hello, I’m posting here as a last resort because this situation is becoming extremely concerning. I applied for the Apple Developer Program on April 1st, and the $99 payment was successfully charged immediately. I was told I would receive a response within 2 business days. It has now been 23 days, and I have received absolutely no communication from Apple—no confirmation, no update, nothing. I have already: Sent multiple emails to Apple Developer Support Waited far beyond the promised timeframe But there has been complete silence. To make things worse, I am located in a country where phone support is not available, so I have no way to escalate this directly. At this point, I’m struggling to understand what’s happening: Apple has taken my payment My developer account is still not active There is no response from support This feels extremely unprofessional and honestly raises serious concerns about how this process is being handled. If there is an issue with my enrollment, why has there been no communication at all? And if not, why is my payment being held without any progress? I would really appreciate if someone from Apple could look into this urgently or advise on what steps I can take next. Right now, I feel completely scammed with no visibility into what’s going on.

My app is: 6757429647, Most of reviews went successfully within 2 days but this one its waiting for review for almost 6 days, what might be the issue? I'm waiting for a reply from Apple team

Hi, I have an approved com.apple.developer.family-controls entitlement for my main app bundle (com.maxflame.prove-it) and submitted a request on April 18, 2026 to extend it to an embedded extension: com.maxflame.prove-it.DeviceActivityMonitorExtension Request ID: 65CKJZ7DQ4 — status still shows "Submitted" with no further response. The extension uses DeviceActivity callbacks and needs to decode FamilyActivitySelection, which requires the entitlement on the extension bundle as well. In my experience, Family Controls entitlement approvals for the main app bundle have come through within 24 hours. It's now been 5 days with no response for this extension request, which seems unusual. Has anyone else gone through this for extension bundle IDs? Did you need to submit a separate request per bundle, or did Apple extend the approval to your extensions automatically once the main app was approved? And has anyone else experienced longer wait times specifically for extension bundles? Any guidance appreciated.

I was selected as one of the winners for the recent Swift Student Challenge, and I was wondering if we will get more information regarding the delivery of the AirPods Max 2 and the certificate? Were these already delivered? I haven't received any email about this, so I wanted to ask here.

I've already submitted multiple cases about this issue. My Family Controls Distribution request was apparently approved (or I was told via Developer Support) for my Shield Action & Shield Configuration extensions, but the Distribution option still does not appear in the identifiers. This is blocking my ability to distribute via TestFlight. I need someone who can update the identifier capabilities or explain why the approved capability is not showing.

On iPad OS 26, the custom keyboard works correctly with a full keyboard, but with a floating keyboard, there is only one line and the console displays a constraint error. Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. ( "<NSLayoutConstraint:0x600002172c10 V:|-(10)-[TUIKeyboardContentView:0x1039c5410] (active, names: '|':TUIKeyplaneView:0x1039c3e20 )>", "<NSLayoutConstraint:0x600002172c60 V:[TUIKeyboardContentView:0x1039c5410]-(-11)-| (active, names: '|':TUIKeyplaneView:0x1039c3e20 )>", "<NSLayoutConstraint:0x6000021721c0 V:|-(0)-[TUIKeyplaneView:0x1039c3e20] (active, names: UIKeyboardLayoutStar Prev...:0x105160e00, '|':UIKeyboardLayoutStar Prev...:0x105160e00 )>", "<NSLayoutConstraint:0x600002172210 V:[TUIKeyplaneView:0x1039c3e20]-(0)-| (active, names: UIKeyboardLayoutStar Prev...:0x105160e00, '|':UIKeyboardLayoutStar Prev...:0x105160e00 )>", "<NSLayoutConstraint:0x6000021728a0 V:|-(0)-[UIKeyboardLayoutStar Prev...] (active, names: UIKeyboardLayoutStar Prev...:0x105160e00, '|':UIKeyboardImpl:0x109905fa0 )>", "<NSLayoutConstraint:0x6000021728f0 V:[UIKeyboardLayoutStar Prev...]-(0)-| (active, names: UIKeyboardLayoutStar Prev...:0x105160e00, '|':UIKeyboardImpl:0x109905fa0 )>", "<NSLayoutConstraint:0x600002177980 '_UITemporaryLayoutHeight' UIKeyboardImpl:0x109905fa0.height == 0 (active)>", "<NSLayoutConstraint:0x600002172df0 'TUIKeyplane.height' TUIKeyboardContentView:0x1039c5410.height == 217 (active)>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x600002172df0 'TUIKeyplane.height' TUIKeyboardContentView:0x1039c5410.height == 217 (active)> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful. iPad OS 26 custom keyboard, full keyboard mode is working normally.

Hey everyone, Back in 2022 and 2023, we noticed that some images on our web pages would disappear randomly. After refreshing, some of the images that were missing would appear, but then another image would go missing. Did anyone else experience this issue? Is there a fix / workaround I can use? This only seems to be an issue on iOS devices and images that have the loading=“lazy” attribute.

I'm writing a read-only filesystem extension. I see that the documentation for loadResource(resource:options:replyHandler:) claims that the --rdonly option is supported, which suggests that this should be possible. However, I have never seen this option provided to my filesystem extension, even if I return usableButLimited as a probe result (where it doesn't mount at all - FB19241327) or pass the -r or -o rdonly options to the mount(8) command. Instead I see those options on the volume's activate call. But other than saving that "readonly" state (which, in my case, is always the case) and then throwing on all write-related calls I'm not sure how to actually mark the filesystem as "read-only." Without such an indicator, the user is still offered the option to do things like trash items in Finder (although of course those operations do not succeed since I throw an EROFS error in the relevant calls). It also seems like the FSKit extensions that come with the system handle read-only strangely as well. For example, for a FAT32 filesystem, if I mount it like mount -r -F -t msdos /dev/disk15s1 /tmp/mnt Then it acts... weirdly. For example, Finder doesn't know that the volume is read-only, and lets me do some operations like making new folders, although they never actually get written to disk. Writing may or may not lead to errors and/or the change just disappearing immediately (or later), which is pretty much what I'm seeing in my own filesystem extension. If I remove the -F option (thus using the kernel extension version of msdos), this doesn't happen. Are read-only filesystems currently supported by FSKit? The fact that extensions like Apple's own msdos also seem to act weirdly makes me think this is just a current FSKit limitation, although maybe I'm missing something. It's not necessarily a hard blocker given that I can prevent writes from happening in my FSKit module code (or, in my case, just not implement such features at all), but it does make for a strange experience. (I reported this as FB21068845, although I'm mostly asking here because I'm not 100% sure this is not just me missing something.)

Hi All, I’m trying to get my app approved that performs a few standard, well-established medical calculations including dosing. It was rejected for 1.4.2 Safety - Physical Harm. I’m confused because I can see dozens of published apps from developers and private companies that perform dose calculations and don’t appear to meet the 1.4.2 standard. Does anyone know what these developers might be doing differently that they are able to gain approval for their apps? Replying to the message in App Connect just got me what looks like a boilerplate answer. I want to be in compliance but it frustrating that I can’t get specifics on how to gain approval.

Dear all, I am not able to transfer a programm to my iPhone 17, i get a certificate issue. Although i followed the general steps. If I was guided to this forum by the german apple support. Before in macOS Sonoma, with iOS 16 and iPhone 8 i have been able building programs for the iPhone. The Simulator has still no issues and works fine. Problem/Error: Certificate installation failed Installing a certificate in the keychain failed (Error Domain=DVTSecErrorDomain Code=-25295 "The specified keychain is not a valid keychain file." UserInfo={NSLocalisedDescription=The specified keychain is not a valid keychain file.}) No profiles for '-.delme2' were found Xcode couldn't find any iOS App Development provisioning profiles matching '-.delme2'. Furthermore, when I try to download a certificate myself via (https://developer.apple.com/account/resources/) I get the error: Unable to find a team with the given Team ID 'XXXXXXXCENSORED' to which you belong. Please contact Apple Developer Program Support. https://developer.apple.com/support In XCode I continue to receive the following information: So no programs can be transferred to my mobile phone. Objective: How do I get the reported errors resolved to transfer programs to my mobile phone?

We are seeing an issue after updating iPads to iPadOS 26.4 where cellular service is lost until network settings are reset. Environment: Devices managed via Apple Business Manager and Microsoft Intune Carrier: Verizon Confirmed affected devices: iPad (9th generation) eSIM Behavior: After update, device shows no cellular service No prompt to re-activate or re-add the cellular plan The plan appears to still be present on the device Workaround observed: Resetting Network Settings restores service Notes: This does not appear to be a provisioning issue (no need to re-add eSIM) Behavior suggests the cellular/eSIM state may not be initializing correctly after update Toggling Cellular or Airplane mode has not yet been tested for service restoration. We have not yet confirmed whether devices using a physical SIM are affected Still gathering data on scope across additional iPad models Additional observation: We have not observed this behavior on iPhones (e.g., iPhone 16 on iOS 26.4 with LTE remains unaffected) Has anyone else observed similar behavior on iPadOS 26.4, particularly on managed devices or eSIM configurations?

AppleOS 26 introduces LowLevelInstanceData that can reduce CPU draw calls significantly by instancing. However, I have noticed trouble with animating each individual instance. As I wanted low-level control, I'm using a custom system and LowLevelInstanceData.replace(using:) to update the transform each frame. The update closure itself is extremely efficient (Xcode Instruments reports nearly no cost). But I noticed extremely high runloop time, reach around 20ms. Time Profiler shows that the CPU is blocked by kernel.release.t6401. I think it is caused by synchronization between CPU and GPU, however, as I am already using a MTLCommandBuffer to coordinate it, I don't understand why I am still seeing large CPU time.

Hello Support Team member - I hope you are having a good day. My app has been approved and I manually released it 8 hours ago. Currently users do not see the subscriptions available on the paywall, and the subscriptions do not show up under in-app purchases in the app store. When I look at my subscriptions in AppStoreConnect - they say "Missing Metadata". When I look inside the subscriptions - one of the two has a localization that is showing a status of "Prepare for Submission". The other subscription does not have a localization - and there is nothing within the subscription that has a yellow warning alert. How can I resolve this? Thank you much!

Hello, i'm currently working on improving accessibility in my app using the built-in Xcode tool, Accessibility Inspector. For the most part, it works well — it correctly displays warnings about missing button labels or insufficient touch target sizes. However, it does not seem to handle certain cases properly, particularly dynamic fonts. Here is the approach I’m using for dynamic fonts: static func getDynamic(font: FontType, size: CGFloat, textStyle: UIFont.TextStyle) -> UIFont { let customFont = UIFont(name: font.rawValue, size: size)! return UIFontMetrics(forTextStyle: textStyle).scaledFont(for: customFont) } label.adjustsFontForContentSizeCategory = true My labels are configured with: numberOfLines = 0 no fixed height constraints This allows them to expand as needed without clipping. I have tested this visually on multiple devices, and everything appears to work correctly — fonts scale as expected, and text is not truncated. However, Accessibility Inspector still reports issues related to dynamic type and, in some cases, text clipping. On iOS 18, approximately 40% of the fonts configured this way still trigger warnings about missing dynamic type support, even though they scale correctly. On iOS 26+, the issue becomes consistent — every font in the app triggers this warning. There are no cases where the inspector passes without reporting a problem, despite the UI behaving correctly in practice. So my question is: Is there a known way to resolve this? Could this be an issue with Apple's tools? If so, is there any information on when it might be fixed?

Hi everyone, yesterday I updated my macOS and Xcode to the latest versions and today I have the strangest thing: Canvas is always crashing whenever I click it, in any and all my Projects. The full Simulator works just fine; only the Preview Canvas crashes. All the crash reports say it's because of AXRemoteElement-BackgroundFetch, and ChatGPT says it's not because of my code. These are very simple Projects, just for experimentation. Nothing complex, just native code while I follow examples in a SwiftUI book. Anyone else having this issue? Translated Report (Full Report Below) ------------------------------------- Process: PreviewShell [2179] Path: /Volumes/VOLUME/*/PreviewShell.app/PreviewShell Identifier: com.apple.PreviewShell Version: 16.0 (23.40.29) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd_sim [1405] Coalition: com.apple.CoreSimulator.SimDevice.E9525D59-3C07-43F9-ACC9-18CF5DD0DAA1 [1516] Responsible Process: SimulatorTrampoline [1120] User ID: 501 Date/Time: 2026-03-26 15:00:02.6060 +0200 Launch Time: 2026-03-26 14:57:33.8870 +0200 Hardware Model: Mac17,9 OS Version: macOS 26.4 (25E246) Release Type: User Crash Reporter Key: 1DC4EA68-804A-D651-804B-C2E0C13D9B87 Incident Identifier: F3F1A52F-AFF9-4470-A216-7364FCB5B7E6 Time Awake Since Boot: 1100 seconds System Integrity Protection: enabled Triggered by Thread: 4, Dispatch Queue: AXRemoteElement-BackgroundFetch Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Subtype: KERN_PROTECTION_FAILURE at 0x000000016b6bfff0 Exception Message: Could not determine thread index for stack guard region Exception Codes: 0x0000000000000002, 0x000000016b6bfff0 Termination Reason: Namespace SIGNAL, Code 10, Bus error: 10 Terminating Process: exc handler [2179]

Hi, My app MediaForge (Bundle ID: uk.mediaforge.app) was approved and is live on the Mac App Store as v1.1.2, however my in-app purchases have been stuck in "Waiting for Review" for 6 days with no movement. Product IDs: uk.mediaforge.app.annual uk.mediaforge.app.lifetime During submission I encountered a known issue where the "In-App Purchases and Subscriptions" section was completely missing from the version page in App Store Connect, making it impossible to formally attach the IAPs to the build before submitting. I have seen other developers report the same bug on these forums. The app is live and customers are unable to make purchases as a result. I have raised a support ticket but have had no response. Has anyone else experienced this recently? Is there anything I can do to progress this, or does it simply need Apple's review team to action the pending IAPs? Any help appreciated. Thanks in advance.

Started 4 weeks ago, can't submit new apps even now. Waiting for "we are looking into it." with no follow up. Thank you,

Body: I'm experiencing a persistent issue that has affected multiple apps I've developed, and I'm hoping to get some guidance from the community or Apple engineers. The Problem: When testing In-App Purchases, my app never enters the sandbox environment. The payment prompt does NOT show the "[Environment: Sandbox]" indicator, and I always receive error code -100 (Invalid Product Identifier). This issue has occurred across multiple apps I've built, including a previous app that I ultimately had to release as a paid download (rather than freemium with IAP) because I couldn't resolve this same problem. Now I'm facing the identical issue with my new app, "AI Job Assistant". What I've Checked (all correct): ✅ Paid App Agreement status is "Active" in App Store Connect ✅ Bundle ID matches exactly between Xcode/HBuilderX and App Store Connect ✅ Product IDs in code match those created in App Store Connect (case-sensitive, no spaces) ✅ All IAP products have complete metadata (name, description, pricing, 640x920 screenshot) ✅ Product status is "Ready to Submit" (not "Waiting for Review") ✅ I have both iOS Development certificate and iOS Distribution certificate — I am using the Development certificate for testing ✅ My provisioning profile is explicitly for Development (named "aijobDevprofile", shows "iOS Development" type) ✅ The Development profile contains my test device UDID ✅ I have fully signed out of my real Apple ID in Settings → Media & Purchases ✅ I only log into my Sandbox Tester account through the purchase prompt (not in Settings) ✅ I test on a real device (not simulator) ✅ I have tried creating multiple new Sandbox Tester accounts ✅ I have tried toggling "Cleared for Sale" off and on for all products ✅ I have waited over 24 hours after making configuration changes What I See: When I initiate a purchase, the payment prompt comes up but there is NO "[Environment: Sandbox]" text anywhere After entering my Sandbox Tester credentials, the request fails with error code -100 (Invalid Product Identifier) My Setup: Development framework: uni-app / HBuilderX (custom debug base with Development certificate and Development provisioning profile) Backend: Cloudflare Workers (handles receipt verification) Testing device: iPhone (latest iOS version) The same issue occurred with my previous app, which I never resolved and eventually gave up on IAP entirely Question: Why does my app never enter the sandbox environment despite using the correct Development certificate and Development provisioning profile? Is it possible there is an issue at the Apple developer account level that is preventing sandbox environment activation? How can I force my debug builds to connect to sandbox instead of production? I am willing to provide any additional logs or information needed. Please help. Thank you.

I enrolled in the individual Apple Developer Program last Thursday and completed the payment, but my enrollment status is still showing as “pending.” To avoid any verification issues, I have already updated my Apple ID name to match my passport exactly. It has now been several days without any update or progress. I’m concerned that something may be blocking the verification process. Could someone please help check my enrollment status or advise on what I should do next? I would greatly appreciate any assistance, as the delay is affecting my ability to proceed with development. Thank you in advance.

Hello, I have a few questions regarding App Store featuring nominations. -When do applicants receive a response to their nominations? -How is this response provided? Is it via the App Store Connect app page, email, or the nominations section? -For an already published app, can an application for App Launch Nomination submitted 1-2 days after publication be accepted? It says applications must be submitted 3-4 weeks before publication. Thank you for help.