Hi, I recently received a Pending Termination Notice from the Apple Developer Program, citing evidence of dishonest or fraudulent activity and a violation of Section 3.2(f) of the Apple Developer Program License Agreement. I believe this action may have been triggered by a mistaken device or network association with my brother’s developer account, which was previously terminated. While we did use the same MacBook and iPhone/iPad for testing in the past, we are completely separate indie developers with different Apple IDs, apps, and publishing histories. All of my apps are 100% original, built over the past 5 years with significant time and effort. I’ve already prepared a full appeal that includes: Proof of identity confirming we are two different individuals A detailed explanation of the historic device overlap A strong commitment to compliance, including use of dedicated devices, accounts, and networks moving forward Before I submit, I’m hoping to ask: Is there any way to ensure my appeal will be reviewed by a human and not auto-dismissed? Has anyone experienced a similar issue and successfully resolved it? Is there a direct way to reach Developer Relations or App Review for edge cases like this? I’m fully committed to adhering to Apple’s guidelines and would greatly appreciate any opportunity to resolve this misunderstanding. Thank you for your time and any help

I've got an app that uses WebRTC. When I try to upload it using Xcode I get the following error: Validation failed The app references non-public selectors in Payload/{MyApp}.app/{MyApp}: initWithURLStrings: (ID: 61a6dbe5-dac2-4910-a836-b4b9b2e891b4) This API is not private, it's just unfortunate that WebRTC chose to use this name as well, and it is falsely identified as a private API by Apple. Has anyone seen this? The funny thing is, I have the exact same app with different configuration in TestFlight internal only for staging, and I could upload it without any issues. And yes, I've tried uploading this app for test flight internal only. No success either.

I have been trying for almost a week to get my app approved. It is like the Submission team doesn't even read my notes. The first complaint is that my app was for a specific business and shouldn't be for the general public. This is true, so I put in the notes that I had requested private distribution and I filled out the request for the app to be distributed privately. The review notes say that I need to distribute my app privately. This is very frustrating. Also, they say the login button doesn't work. It works for everyone that uses it in the Test Flight. One nuance we have is that our servers will not respond to IP addresses that orginate outside of the US. I have this in caps in the notes. They still say that the Login button doesn't work. The app was written for iPhones, yet they keep testing it on an iPad. There doesn't seem to be any way to communicate with the submission team other than through the test notes and they don't seem to be reading these. Can anyone direct me to where I can get some help on this? Thanks, Jim

My app keep getting rejected after changing complete UI. It's an finance tool app. any advice Guideline 4.3(a) - Design - Spam We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts

Hello everyone, I build and run the app in iPhone in developer mode but now i am trying to install and run the app in another iPhone in which i did not turned on the developer mode. it installed but not opening without the Developer mode. Is there any another way to install and run the app with Developer mode for one time. If not then tell me the process how i can do publishing in testFlight or appStore. Thanks

Hello, I’m an iOS developer and the original creator of the app "Instant Save: Reels story" (App Apple ID: 6469411763). On July 5, 2025, I received two Apple emails saying the app was transferred to another developer account. However, I did not initiate or approve this transfer. My Apple Developer account has Two-Factor Authentication enabled, and I received no OTP or request for approval. I submitted a legal dispute form via Apple’s Intellectual Property page on July 7, 2025, but I’ve only received an automated acknowledgment — no dispute number or follow-up. I’ve also contacted Apple Developer Support multiple times by phone, but they confirmed they cannot escalate legal cases or access my dispute status. Has anyone else faced this issue recently? I’m looking for any guidance or similar experiences while I await a response from Apple Legal. Thanks in advance,
 Bhautik Amipara

Hello Apple Developer Support & Community, I’m reaching out regarding the unexpected termination of my Apple Developer Program account, associated with App ID: 6744330283. Recently, my app was flagged under Guideline 4.3 - Spam, and I was asked to make necessary changes. I followed all guidance provided by Apple, including a phone call with an App Review team member, who clarified the steps I should take. I did not submit any further update after that call. However, before I had the chance to upload the new, compliant version of my app, my entire developer account was terminated without a clear explanation or additional warning. I believe this was a misunderstanding, as I was actively working on compliance and fully committed to resolving the issue. My app is not spam I only followed Apple’s instructions I never uploaded a new version after my call with App Review No specific violation or example of “spam” was shown to me I’ve submitted an official appeal via the App Review Board, but I’m hoping someone here can also assist or escalate this matter. My developer account and years of effort are at risk over what seems to be a miscommunication. Thank you for any guidance or assistance you can provide.

My app published 6 hours ago this is first version and IAP is still in review. My app is hard paywall app so people cannot continue in app and this is all happening during initial boost. I contacted with apple but they say they send message to review time and hours passed nothing changed. People downloading the app and I'm watching it without able to do anything :( Are there anyone experienced same thing ? Do you have any advice ?

Hello, Since updating to iOS 26 Beta 3, I’ve been experiencing an issue where transactions purchased through the normal in-app purchase flow continue to be reported as updated and unfinished—even after calling the finish() function. Please resolve this promptly.

Hi all, I submitted a healthcare-related iOS app on June 19 that integrates with a health monitoring device. It had a few prior rejections due to compliance concerns, which we addressed. Apple Developer Support confirmed the review is still in progress and that it requires additional time. I'm wondering if others have experienced similarly extended review timelines for healthcare or medical device-integrated apps, and how long it took for resolution. Would appreciate any advice or shared experiences on this. Thanks!

After posting a new version of our app, we used to have 80% of our userbase on the new version pretty quickly (usually 72 hours, sometimes less). Over the past few weeks, we've noticed that the App Store has throttled down app updates, and it now takes much longer for a new version of our app to reach 80% (approximately 15 days, so 5 times slower). He is an update graph before: And a similar update graph after: We've published several versions over the past couple of weeks, and we've seen the same slow update behavior for all of them. What could explain these differences ? At the time of this writing, the update graph has very slowly reached 80% and is now flat. In the past it would easily reach 90% (the last 10% were always slow to get).

Hi, Our recent security scans, performed by Data Theorem, have flagged a potential App Store blocker related to the use of a private iOS class, NSBlock. We are concerned that this identified warning may lead to our apps being rejected during the next App Store submission. Issue Summary: We integrate a library, this SDK is developed using Kotlin Multiplatform, and during compilation, Kotlin automatically generates Objective-C/Swift interoperability code. As a result of this code generation, the compiled framework includes a reference to a private Apple class, NSBlock. It’s important to note that: No methods or functionality from NSBlock are being invoked or used. This reference is auto-generated by Kotlin’s ObjCExport.mm module. For additional context, you may refer to a related discussion on this issue: https://github.com/ricohapi/theta-client/issues/98 https://github.com/JetBrains/kotlin-native/issues/1642 https://github.com/JetBrains/kotlin-native/pull/1652/files We would like to confirm whether the presence of this unused reference to NSBlock will result in the rejection of our application during App Store review. Thankyou

Hello Apple Developer Team and Community, I’m writing to raise a serious concern regarding my app (App ID: 6744330283) which is now being repeatedly rejected under Guideline 4.3 (A) – Spam, despite being previously approved and published for at least two earlier versions. We have had multiple rounds of communication with the App Review team in the past, carefully addressing every request and making adjustments accordingly. These previous versions were reviewed and approved without any reference to 4.3 issues. However, since a recent update, we’ve been receiving rejections citing Spam 4.3 (A) — without any specific explanation or detailed reasoning. Even more frustrating: Each review now takes over a week to process, making our release cycle extremely difficult to manage. It required dozens of phone calls and emails just to get the app reviewed at all. I even had a meeting with an App Review team member, where I was told: “The recent updates are considered Spam 4.3, while the earlier versions that were approved are not.” But I am truly confused by this, because all the updates share the exact same codebase — there are no material differences between the approved versions and the ones now being rejected. This inconsistency and lack of clarity is making it impossible for us to move forward. We respectfully request: A clear and actionable explanation for why the recent versions are now considered Spam 4.3 (A), while earlier versions were not. Specific guidance or examples to help us understand what triggered this new interpretation. Transparency about what exactly changed — either in review criteria or policy enforcement — so that we can comply properly. We are committed to fully adhering to the App Store Review Guidelines and improving the app accordingly, but we can’t do that without transparency and fair communication. Any insights from the Apple team or other developers who’ve faced similar issues would be greatly appreciated. Thank you.

FB17250415 was also filed, please help me. Reproduce Version: Macos 15.3.2 and above. Reproduce Steps: Download and run the following desktop watermark app(attachment); 2.After the watermark app running a watermark window is showing at the left top corner. 3. Open App Store and try to install any app, after the confirm installation dialog appears, move the App Store window to desktop watermark area, the confirm installation button will disapper. #import <Foundation/Foundation.h> #import <Cocoa/Cocoa.h> int main(int argc, const char * argv[]) { @autoreleasepool { // insert code here... NSLog(@"App started"); //TODO1:Get current screens and get screen's NSRect NSScreen *screen; NSRect frame = NSMakeRect(0, 0, 1000, 1000); NSWindow* window = [[NSWindow alloc] initWithContentRect:frame styleMask: NSWindowStyleMaskTitled //0x80 backing:NSBackingStoreBuffered defer:NO]; // ant-setttings [window setAcceptsMouseMovedEvents:NO]; //[window setFloatingPanel:true]; ==> only valid for NSPanel //0x111 = 1 << 0 | 1 << 4 | 1 << 8 [window setCollectionBehavior:NSWindowCollectionBehaviorCanJoinAllSpaces | NSWindowCollectionBehaviorStationary | NSWindowCollectionBehaviorFullScreenAuxiliary ]; [window setMovableByWindowBackground:YES]; [window setExcludedFromWindowsMenu:YES]; // [window setAlphaValue:0x3FF0000000000000]; [window setOpaque:NO]; [window setHasShadow:NO]; [window setHidesOnDeactivate:NO]; [window setLevel:NSScreenSaverWindowLevel]; [window setIgnoresMouseEvents:YES]; [window setReleasedWhenClosed:NO]; [window setStyleMask:NSWindowStyleMaskBorderless]; // get screen rect and set to NSWindow [window setFrame:frame display:YES animate:NO]; [window setMovable:NO]; //Step1. Create a NSImage object with user-infomation embedded; ==> get this done NSSize size; size.width = 100; size.height = 300; NSImage* watermark_image = [NSImage imageWithSize:size flipped:NO drawingHandler:^(NSRect dstRect) { NSGraphicsContext* current_ctx = [NSGraphicsContext currentContext]; [current_ctx saveGraphicsState]; //current_ctx = [NSGraphicsContext currentContext]; CGContextRef context = [current_ctx CGContext]; //Rotates the user coordinate system in a context. CGFloat tilt_angle = 20*M_PI/180; CGContextRotateCTM(context, tilt_angle); NSString* data = @"12345"; NSPoint point; point.x = 20; point.y = 0; NSFont *font = [NSFont fontWithName:@"Arial" size:20.f]; NSDictionary *attributes = [NSDictionary dictionaryWithObjects: @[font, [NSColor redColor]] forKeys: @[NSFontAttributeName, NSForegroundColorAttributeName]]; [data drawAtPoint:point withAttributes:attributes]; [current_ctx restoreGraphicsState]; return YES; }]; //Step2. Create a UIColor object based on the NSImage object created above; NSColor* backgroud_color = [NSColor colorWithPatternImage:watermark_image]; //Step3. Set the new UIColor object as NSWindow background; [window setBackgroundColor:backgroud_color]; // TODO:Double check again; [window makeKeyAndOrderFront:NSApp]; CFRunLoopRun(); NSLog(@"App ended"); } //sleep(10*1000); return 0; }

We are implementing an Advanced App Clip Experience for our App Clip, but encountered a blocking issue where the configuration is shown as valid in App Store Connect, but is not recognized on device. We have run out of ways to debug and would appreciate help. Setup Summary Our main app is live on the App Store and includes an App Clip target. The Advanced App Clip Experience is configured in App Store Connect Status: Received Domain validation: All checks are marked as passed ✅ The domain's AASA (apple-app-site-association) includes the correct App Clip bundleID. ❌ The Issue When scanning a QR code pointing to outs domain on an iPhone The App Clip card does not appear. 2.Using the Developer > App Clip Experiences > Diagnostics tool on iPhone, entering the domain returns: "No Advanced Experience is registered for this URL." I’m very confused about why the device behavior doesn’t match the configuration status in App Store Connect. Any insight or suggestions would be greatly appreciated!

Hi everyone, I’m seeing a consistent one-day discrepancy between the expiresDate returned by the App Store Server API and the “Expires on” date shown in the iOS Settings / App Store subscription list. I’d like to confirm whether this behavior is expected or if I’m misunderstanding the way Apple rounds dates. Reproduction steps Step Action Result 1 Purchase a 1-month auto-renewable subscription on 23 June 2025 14:00 JST (UTC+9) Transaction succeeds 2 Immediately fetch the transaction with GET /inApps/v1/subscriptions/{transactionId} Response contains "expiresDate": "2025-07-23T05:00:00Z" (= 23 July 2025 14:00 JST) 3 On the same device open Settings › Apple ID › Subscriptions (or App Store › Account › Subscriptions) UI shows Expires on: 22 July 2025 The same happens for every monthly renewal and on multiple devices. Region is Japan, device time zone Asia/Tokyo. What I understand so far (and my hypothesis) Apple’s docs say a monthly subscription renews “on the same calendar date” of the next month, so renewal in this example is 23 July. If the renewal is scheduled for 23 July at 14:00 JST, the subscription is fully usable until the end of 22 July in calendar terms, because the new billing period starts the moment the 23rd begins in Apple’s canonical time zone. Therefore, it might be intentional for the UI to display 22 July—i.e., “you can keep using it through the 22nd; on the 23rd it renews.” This hypothesis makes sense internally, yet it still looks confusing to end users who read “Expires on 22 July” and assume access ends at 00:00 on the 22nd, a whole day earlier than in reality. Questions Is showing the day before the renewal date the official/expected behavior? If so, could Apple clarify that the “Expires on” label represents the last full calendar day rather than the exact expiry timestamp? Which value should we surface in-app when telling users “Your subscription is valid until …”? The server’s expiresDate (precise to the second, converted to user time zone), or A UI-style date that’s one day earlier, matching Settings / App Store? Does Apple have a public document describing this rounding/visual convention? Have other developers encountered user confusion about the apparent 1-day “shortening” and, if so, how did you word your in-app messaging? Any insight from Apple engineers or fellow developers would be greatly appreciated. Thank you!

Hi, One of my application doesn't get rating updates on AppStore. On https://appstoreconnect.apple.com/ Ratings and Reviews page I see that app got 19 Ratings with average 3.8 out of 5. But on AppStore it just have 5 ratings with average 3.4 out of 5. See attached screenshots: AppStore: AppStore Connect: . Please help me to figure out with this issue and hope we can fix rating on AppStore page accordingly to AppStore Connect. Thanks, Alex

I'm developing a visionOS app and was able to upload new builds without any problems to the App Store. A couple pf days ago I wanted to ship another update, but now I can't submit it to the App Store anymore, because the validation failed, something related to the App Icon seems to be the issue, the logs mention CFBundleIcons.CFBundlePrimaryIcon. I have setup the App Icons here: The validation error I first got was this, mentioning a plist entry (that has not been necessary in the past) is missing. I've then added that plist entry, as described in the reference doc for CFBundleIcons.CFBundlePrimaryIcon. My info.plist now includes this, following the mentioned docs: However, now I get a type missmatch error when validating — however the types are as described in the docs: What am I missing? Why even is this plist entry required now? Or is this a Bug? Help please

Hello, I submitted an appeal after my app was rejected under Guideline 4.3(a). It has now been over 5 days and I have not received any reply from the App Review Team. Has anyone experienced similar delays recently? Does Apple respond eventually or is there something else I should do? Thank you in advance.