Overview

Hi everyone, Recently, a user purchased an annual subscription in one of my apps but hasn’t used the service much (I track usage through my backend). The user emailed me saying the purchase was made by mistake and had already submitted refund requests through the report portal. However, the requests were declined twice, and they can no longer submit another refund request. I suspect this may be because, in RevenueCat, I previously set the developer preference for refunds to “Prefer to decline,” due to users abusing AI trials. I have since changed the refund preference to “Prefer to grant,” but the user is no longer able to request a refund. May I know how I should proceed in this situation? I’ve already contacted Apple, but I’d appreciate hearing how others handle similar cases. Thanks!

Dear Apple Support Team, I purchased an Apple Developer account, but it has still not been approved even after 8 days. I have sent more than 10 emails regarding this issue, but I have not received any response so far. I kindly request you to look into this matter and resolve it on priority.

Hello, I recently submitted an update for my app, and I would really appreciate it if you could review it when possible. The latest version includes important fixes and improvements. Please let me know if anything else is needed from my side. Thank you for your time and support.

Hello everyone, I’m facing a persistent App Store rejection under Guideline 2.1(b) – App Completeness, related to In-App Purchases, and I’m unable to reproduce the issue on my end. Issue reported by Apple Review Apple Review team reports: “No action occurred when we attempted to buy the subscription.” Device: iPad Air 11-inch (M3) OS: iPadOS 26.4.1 What I have verified from my side I have thoroughly tested the subscription flow under multiple scenarios: Sandbox Testing Using sandbox test accounts Product loads correctly Purchase flow completes successfully Apple payment sheet appears properly TestFlight Testing Installed app via TestFlight Logged in with real Apple ID (Beta tester) Successfully completed subscription purchase Device Testing Tested on multiple iPhones Tested on iPad as well Purchase flow works correctly on all devices App Store Connect Configuration Paid Apps Agreement → Active Banking & Tax → Completed (no pending warnings) In-App Purchase status → “In Review” Product is correctly configured and attached to app What Apple is experiencing Based on their feedback and screenshots: Subscription screen loads correctly Product price is visible When tapping “Subscribe Now” → no action occurs No error message, no purchase sheet Is there a recommended workaround or reviewer instruction to avoid this deadlock? Any insights or real-world experience would be greatly appreciated. Thanks in advance.

Hello Apple Developer Support, I would like to follow up regarding my Apple Developer Program enrollment. I have two order numbers: D004762197 (failed payment attempt on Tuesday, April 14, 2026) D004767639 (successful payment on Thursday, April 16, 2026, invoice received) Currently, my account is still showing "Pending" and asking to complete the purchase, even though the second payment was successful. It seems my account might still be linked to the failed order. Could you please help link the successful payment and activate my account? Thank you very much.

My current app is a smoking cessation app and it is desgined to help people quit smoking for good. Currently users of the app are expected to set a quit date and then remain quit from cigarettes for 12 weeks. The app helps with this by using badges, notifications and even live chats to stop smoking professionals (depending on your area). The app "frequently" mentions smoking and tobacco, but it never promotes it. It does the opposite. By mentioning the harms of smoking and the benefits of stopping. The app also mentions (and can provide, depending on your area, medical history and a professionals final opinion) about nicotine replacement therapy, which users who are quitting smoking may be interested in. Currently the app is rated 18+ as I have to tick "frequent" mention of drugs/tobacco/alcohol in the age rating questionnaire. Though it does not mention recreational drugs or alcohol. We will soon be adding a large update to the app to add vaping support. The app will change largely in the fact smoking content and vaping content will be siloed from each other. So a user can either be on a smoking support journey (and see stop smoking content), or a vape support journey (and only see vaping content). We need the app to be 13+ on the store and we will enforce age restrictions using the declared age range API as part of the account creation process. If the user is aged 13 - 17, they will only see vape related content, if they are 18+ they can see vaping OR smoking. How negotiable is the age rating certificate, can we change it to 13+ if we implement age restrictions in the app and protect stop smoking related content behind it?

I’m looking for guidance on a notarization submission that has been stuck in In Progress for over 24 hours. Details: Team ID: 94B7AVM73F Certificate: Developer ID Application: Bilal Ahmed Qureshi (94B7AVM73F) Tool: xcrun notarytool File: FlashcardGeneratorTrial-AppleSilicon.dmg Submission ID: 7817f9d0-32da-452f-9e2d-fff43478ccf6 Submission created: 2026-04-17T22:10:01.402Z Current status: xcrun notarytool info still reports In Progress This has now been ongoing for more than 24 hours The submission uploaded successfully and received a valid submission ID The Developer ID certificate is valid and correctly paired with the private key in Keychain security find-identity -v -p codesigning returns 1 valid identity Environment: First-time notarization on this developer account macOS direct distribution outside the Mac App Store DMG signed with Developer ID Application certificate Hardened runtime and timestamp enabled during signing I’ve seen some other recent reports of long notarization delays, especially for first-time submissions, so I’m trying to understand whether this is expected queueing / in-depth analysis, or whether there may be an issue with this specific submission. Questions: Is this normal for a first notarization on a new Developer ID account? Is there anything I should do besides wait? Can Apple check whether this submission is stuck in the queue? Thanks.

Hi there is a small extension to my existing app to open a webpage in a web view. The ux team want this webview full screen, relying on a close button loaded by the webpage to exit. No native top bar or control to close. my opinion is this isn’t resilient and could also fail AppStore compliance during submission. A user could get trapped in web view for a number of non happy paths. guidelines seem a little inconclusive but do others have experience of this concern that they could share? Could submission fail review?

Is system_profiler the recommended approach for retrieving installed application data on macOS? If not, what is the preferred and reliable alternative to fetch a consistent and complete list of installed applications?

Hello, Our application has been stuck in the "In Review" status for 17 days now, and we are looking for guidance on whether this is a known technical stall or an extended policy audit. The Issue: The app moved from "Waiting for Review" to "In Review" on March 25th. Since then, there has been no change in status and no messages in the Resolution Center. App ID: 6753868146 Thanks

Somewhere since iOS 26, the LockedCameraCapture framework gets in an unpredictable state after opening the main app from the LockedCamera extension using LockedCameraCaptureSession.openApplication(for userActivity:). (Feedback with sample code to reproduce: FB21966835) Opening the extension from the lock screen again doesn’t open the extension but puts the lock screen in a state as if it has. Content updated from LockedCameraCaptureManager.shared.sessionContentUpdates comes in inconsistently, usually needs the app to be opened again or the extension to be opened. This makes using this extension impossible for me as I use it to record video files that manually need to be imported when the app is launched (so not through PhotoKit). Does anybody have a suggestion to circumvent this issue or how to get this fixed?

I've created a new user under "Users and Access". The first time, the email was sent to the intended user, however when they click the link, they only get spinning wheel. The second attempt was using their personal gmail account. The invitation was sent but has not been received by the team member. This has been tried twice now. Is there anything we can do to get this sorted? Thanks.

Dear Apple Team, I need your help resolving an issue that Apple Support has been unable to fix for over two months. Since February 2026, the Apple Developer app has rejected my identity verification every time I attempt to enroll in the Apple Developer Program. I have reached out to Apple Support repeatedly — by email and by phone — and have received no explanation for the failure and no workable solution. My case numbers from these interactions are: 102818147247 102838793176 102842518632 To be direct: I'm not intend to be aggressive, I just exhausted every normal support channel available to me. The responses I have received so far have been polite but ultimately ineffective — the same suggestions are repeated, and no one has investigated the underlying cause. This is not a minor inconvenience. I run PlayPatch Tech as an small team with iOS apps that are blocked from App Store submission entirely because of this enrollment failure. Every week this remains unresolved is a week of lost business. Relevant details: Enrollment type: Organization Device: iPad Pro & iPadOS 26.3.1(a) Government ID used: China ID Card Timeline: February 2026 – present Support contacts: Email 8 times, Call 6 times, they tried their best, but nothing worked. What I need: Someone with the authority and access to diagnose why verification is failing for my account specifically. An alternative verification path if the app-based method doesn't work. I would appreciate a response within 5 business days. I am available at any time and willing to provide whatever documentation is required. Regards, Neo PlayPatch Tech

Something happened with my Xcode 26.4 install, I've never had this happen before. I get Xcode 26.4 installed, but the simulators aren't installed. And nothing pops up to "install required simulators". In Devices & Simulators I click the + to install a new simulator, and the beachball just spins and Xcode becomes unresponsive. I've tried quitting and restarting Xcode, reinstalling it (using both xcodes command line tool and the app store), removing Xcode and reinstalling, rebooting after removing Xcode and before reinstalling. Not sure what to try next. Feels like something is left over from uninstalling that's hanging it up. But I've no idea what. I could use some Apple Xcode team help here.

Hi, We are evaluating Swift Package Manager for distributing private packages to external customers. Our use case requires enterprise-grade authentication beyond standard username/password, personal access token, or SSH key based authentication. Our current authentication model relies on request signing / IAM-based authorization rather than standard Git credentials. From what we can tell, Swift Package Manager does not appear to expose a built-in mechanism for custom authentication hooks during package resolution. Because of that, we started exploring whether a Git-based workaround might be possible, such as: using a custom Git URL scheme handling that scheme through a Git remote helper using a Git credential helper or related Git configuration for authentication We tried a proof of concept along these lines, but Xcode did not seem to recognize or resolve the package correctly. We are trying to understand what is officially supported and what is not. Our questions are: Does Xcode / Swift Package Manager support package dependencies that rely on custom Git URL schemes? During package resolution, does Xcode honor system Git configuration for remote helpers and credential helpers? Is there any difference in support between: adding the package through the Xcode UI resolving through swift package resolve resolving through xcodebuild For private package distribution, is there any Apple-recommended approach when authentication requires request signing or a custom IAM-based flow instead of standard Git credentials? If custom Git authentication is not supported, should we assume the recommended path is to place an authenticated proxy or gateway in front of a standard Git or HTTPS endpoint instead? We are mainly trying to determine whether this direction is fundamentally unsupported in Xcode / SwiftPM, or whether there is a supported way to integrate enterprise authentication into package resolution. Any guidance would be appreciated. Thanks!

After waiting for review, making changes, then stuck "In Review", I made the major decision to pull my pro audio application from the App Store before it was even accepted. The friction generated from Apple's process is not worth what you are getting back. Consequently, the offering for audio in the Mac App Store itself look very amateur and are largely limited to toys. This is an uninspiring group to be associated with and given the delays, cost, and hamstringing due to sandboxing, the motivation to follow through is very low. I would encourage Apple to rethink their macOS approach if they actually want developers to use this system. This has been an issue for many years, and the situation is not improved. I thought I'd try again this round, but have again given up on the wait and restrictions.

Hi! I'm a first-time app founder trying to enroll my business in the Apple Developer Program as an Organization. I already have a personal Apple ID, so I'm trying to create a separate, brand new Apple Account using my business email for the enrollment. Every time I complete the account creation form and go through the verification code step, I get the error: 'Your account cannot be created at this time.' Things I've already tried: Personal cell phone number for verification A Google Voice number for verification Different browsers The Apple Developer app Different WiFi networks I only have one iPhone and one cell number, both already tied to my personal Apple ID. My D&B DUNS number is confirmed, the only blocker is creating this new Apple Account. Is there a known solution for this? It seems like it must be a common situation for small business owners who use one device for both personal and business. Any help appreciated!

We're experiencing an EXC_BAD_ACCESS (SIGSEGV) crash in UIView.drawHierarchy(in:afterScreenUpdates: false) that occurs only on iOS 26.3.1 and later. It does not reproduce on iOS 26.3.0 or earlier. Crash Stack Thread 0 (Main Thread) — EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0 libvDSP.dylib vConvert_XRGB2101010ToARGB8888_vec 1 ImageIO IIOIOSurfaceWrapper_CIF10::CopyImageBlockSetWithOptions 2 ImageIO IIOImageProviderInfo::CopyImageBlockSetWithOptions 3 ImageIO CGImageReadGetBytesAtOffset 4 CoreGraphics CGAccessSessionGetBytes 5 CoreGraphics img_data_lock 6 CoreGraphics CGSImageDataLock 7 CoreGraphics ripc_AcquireImage 8 CoreGraphics ripc_DrawImage 9 CoreGraphics CGContextDrawImage 10 UIKitCore -[UIView(Rendering) drawHierarchy:afterScreenUpdates:] The crash occurs during 10-bit CIF10 → 8-bit ARGB8888 pixel conversion when the IOSurface backing a UIImageView in the view hierarchy is deallocated mid-render. How to Reproduce Display a scrollable list with multiple UIImageViews loaded via an async image library Call drawHierarchy(in: bounds, afterScreenUpdates: false) on visible cells periodically Scroll to trigger image recycling Crash occurs sporadically — more likely under memory pressure or rapid image recycling What We've Tried Both UIKit off-screen rendering approaches crash on iOS 26.3.1: Approach Result drawHierarchy(afterScreenUpdates: false) EXC_BAD_ACCESS in CIF10 IOSurface decompression view.layer.render(in:) EXC_BAD_ACCESS in Metal (agxaAssertBufferIsValid) iOS Version Correlation iOS 26.3.0 and earlier: No crash iOS 26.3.1 (23D8133)+: Crash occurs (~5 events per 7 days) We suspect the ImageIO security patches in iOS 26.3 (CVE-2026-20675, CVE-2026-20634) may have changed IOSurface lifecycle timing, exposing a race condition between drawHierarchy's composited buffer read and asynchronous IOSurface reclamation by the OS. Crash Data We sampled 3 crash events: Event 1 (iOS 26.3.1): 71 MB free memory — memory pressure Event 2 (iOS 26.3.1): 88 MB free memory — memory pressure Event 3 (iOS 26.3.2): 768 MB free memory — NOT memory pressure Event 3 shows this isn't purely a low-memory issue. The IOSurface can be reclaimed even with ample free memory, likely due to async image recycling. Question Is this a known regression in iOS 26.3.1? Is there a safe way to snapshot a view hierarchy containing IOSurface-backed images without risking EXC_BAD_ACCESS? Should drawHierarchy gracefully handle the case where an IOSurface backing store is reclaimed during the render? Any guidance or workarounds would be appreciated. We've also filed this as Feedback (will update with FB number after submission).

I made the payment for the Apple Developer Program, but my membership is still not activated. On the website, it still said: “Purchase your membership. To continue your enrollment, complete your purchase now.” Since it still showed that message, I thought there might be an error. I clicked “Complete your purchase” again, but then I canceled it because I had already paid before and did not want to be charged twice. Now my membership is still not active, and I am confused about whether my original payment is still being processed or whether I caused a problem by clicking and canceling the purchase flow. I emailed to apple support but still didn't get any answers. Idk what to do.

So I'm working on adding another component to my app that uses NSOutlineView, as we do in AppKit. There will probably always be less than 25 rows here. One row is much larger than the others. Not sure if any of this matters. What I know is I noticed scrolling it is very jank. It's going way too fast. So I took a peek and see lineScroll is getting is 304 in Interface Builder. Not sure how that happened. I changed it to like 24. Then Interface Builder automatically changes it back to 304. So in -viewDidLoad I just set it: NSScrollView *scrollView = self.outlineView.enclosingScrollView; scrollView.verticalLineScroll = 24.0; scrollView.lineScroll = 24.0; But scrolling still is busted. So I subclass NSScrollView and override the setters. For some reason, NSTableView's -tile method is deciding to change the lineScroll to 304, all on its own. So every time tile is called. line scrolls get reset to 304.