Overview

Is there a way to view the opt-in rate via the API? I have been unsuccessful in finding one.

Hi everyone, I'm at the six-week mark of my Apple Developer Program enrollment and feeling pretty stuck. I wanted to post here to see if anyone else has been through something similar — and, hopefully, to get some guidance on what to do next. Six weeks since I submitted my enrollment application. Zero email updates from Apple at any point during this time — no acknowledgment, no status change, nothing. I called Apple Developer support about two weeks ago. The representative told me that additional documents had been requested and submitted on my behalf. That was promising — but since then, complete silence. I have heard nothing further in the two weeks since that call. I understand there can be legitimate delays, especially for organizations or businesses going through identity verification. But six weeks without any proactive communication feels excessive, and it's making it difficult to plan any development work or App Store submissions. Has anyone else experienced a timeline like this? Any insight from folks who've been through a lengthy enrollment would be really appreciated. At this point I'm not sure if I should keep waiting, call again, or try something else entirely. Thanks in advance.

Hi all, Looking for some clarity.. I have an app (Pocket Love: AI Roleplay Chat, Apple ID: 6745031268) that went through a long review process with many resubmissions. The feedback I received across those reviews was often generic “overtly sexual”) message, but without any detail on exactly what needed to change. Because of that, I approached it iteratively making adjustments each time based on what I thought the issue might be. Over time I made quite significant changes across the app (imagery, unlockable content, voice-overs, menus, copy, etc.), and increased the age rating to 18+. I also had a call with a policy eexpert & App Review. In the final interaction, I was asked to ensure all unlockable content was visible, so I re-uploaded a build and provided screenshots with everything pre-unlocked for transparency. Despite this, my account has now been flagged under 3.2(f) for “dishonest or fraudulent activity,” and is pending termination. What I’m struggling to understand is: Can repeated resubmissions / iterative changes alone be interpreted as “evasion” under 3.2(f)? Or does this typically mean App Review believes there was something intentionally misleading? From my perspective, I was trying to respond to feedback and get the app into a compliant state, not bypass review or hide anything. The game does have "sexy" imagery lingerie etc..and adult themes but 0 nudity and is tamer than similar games live on the app store. Would really appreciate any insight from others who’ve experienced similar, or from anyone familiar with how this is interpreted internally. I can't believe my account is pending termination without any intentional wrongdoing, I currently have 3 other live games one with strong revenue, that will be removed too due to this. My initial appeal was rejected today. Thanks!

Hi! I’m facing some difficulties while integrating with Apple external purchase API. I would like to clarify a few points in the documentation. Subscription Events Documentation mentions four subscription events: SUBSCRIPTION_START, SUBSCRIPTION_CHANGE, SUBSCRIPTION_PAYMENT, and RENEWAL. Could you clarify what SUBSCRIPTION_PAYMENT is used for? The examples indicate that we should send the tax and payment amounts in the SUBSCRIPTION_START and RENEWAL events. Should we also send them for SUBSCRIPTION_PAYMENT? 2. Unused Tokens Customers generate ACQUISITION and SERVICE tokens and send them to us. According to the documentation, we must report every token received. If we process balance transactions linked to an ACQUISITION token, should we send the SERVICE token with NO LINE ITEM? Should we continue sending the SERVICE token with NO LINE ITEM status in the following months? 3. Should we send reports only once a month? What should we do if, at the time a transaction is received, the token was active, but by the time the report is due, it has already expired? Do we still need to report it in that case? 4. What should we do if we receive a notification about an unreported token in the middle of the month? Should we send the report immediately, or should we take note of the token and include it in the report at the scheduled time at the beginning of the month? 5. Am I correct in understanding that if a user purchases a monthly subscription and cancels the renewals within the same month, the reports will contain only one event — SUBSCRIPTION_START with subscriptionDaysOfPaidService = 0? If a renewal for a monthly subscription fails and the payment is completed after a 7-day grace period, should we report 37 days or 30 days in subscriptionDaysOfPaidService in the RENEWAL event? Thank you in advance for your guidance!

Hello, My app "Tall - App de rencontre" (App ID: 6761081326) has been rejected 4 times under Guideline 4.3(b) Design Spam. The App Review Board also upheld the rejection (Appeal Ticket APL411770). I fully understand the dating category is saturated. However, my app has unique mechanical features that do not exist on any other dating app on the App Store: MANDATORY HEIGHT GATE: During registration, women below 1.75m and men below 1.80m are blocked and CANNOT complete registration. This is hard-coded into the onboarding. It is not an optional filter. Users who do not meet the height criteria simply cannot use the app. DOOR-FRAME HEIGHT VERIFICATION: Users must submit a full-body photo standing barefoot under a standard door frame to verify their height. Unverified users see all other profiles blurred. This trust-and-safety mechanism is entirely unique. "THE BAKERY": A curated, time-limited daily drop of compatible profiles replacing infinite swipe. This is an anti-swipe paradigm designed to prioritize quality over quantity. I also have an existing community of over 1,000 people across multiple WhatsApp groups TALL FRANCE, 10K Instagram followers, and 44K TikTok followers — all specifically for tall people looking to connect. This proves real demand for this niche. I also noticed that the app "Score Dating" is currently live on the App Store in the Lifestyle category. Score blocks users who do not have a credit score of 675 or above. My app uses the same concept — a mandatory gate based on a specific criteria (height instead of credit score). If Score is accepted, I believe Tall should be evaluated with the same standard. I have responded to every rejection with detailed explanations and visual evidence, but received the same copy-paste response each time. I have a Meet with Apple consultation scheduled to discuss this further. Has anyone successfully overcome a 4.3(b) rejection for a niche app with genuinely unique features? Any guidance from Apple or the community would be greatly appreciated. Thank you, Frankie Babet

Greetings fellow devs, After accepting the Alternative Terms Addendum for Apps in the EU and adding the Storekit External Purchases or Offers capability via App Store Connect in our app identifier, the entitlement showing up in xcode is com.apple.developer.storekit.custom-purchase-link.allowed-regions and has the value 'jp'. How can we change the value for that entitlement to 'gr'? We tried changing it in xcode, but we get the error <Provisioning profile "iOS Team Provisioning Profile: [app identifier]" doesn't match the entitlements file's value for the com.apple.developer.storekit.custom-purchase-link.allowed-regions entitlement.>. In Certificates, Identifiers and Profiles in the developer account there is no way to configure that capability. We sent a request to support and they only gave a link to documentation and to the forum here. We have a completed every business agreement requested and we have chosen Greece as the organisation region and the app's availability region wherever possible. We haven't found anywhere that Japan would be chosen to explain the entitlement given. So where can this entitlement about allowed regions be configured? Xcode version is 16.4 and iOS minimum deployments is 18

I have a SwiftUI view in a watch companion app, and when I build my app with Xcode 26.2 or 26.3, the navigation title on a presented screen disappears after the watch screen goes dark. So, the navigation title is only visible when the screen is first presented and not again after the watch screen goes dark, for example when the user lowers their arm. Please see the screenshots for a better understanding. Notice that the "Bench Press" text is not visible in the third image. Also, I’ve confirmed that this does not happen when the app is built with Xcode 16.4. First Image (initial presentation of the screen): Second Image (watch screen goes dark): Third Image (watch screen goes back on, title missing): Although I've confirmed that this is related to Xcode versioning, and it happens on multiple screens, here is the redacted version of this SwiftUI view that is shown in the screenshots, in case it helps: var body: some View { NavigationStack(path: $viewModel.pushedViews) { TabView(selection: $selectedTab) { ... ZStack { List { ForEach(Array(viewModel.setModels.enumerated()), id: \.element) { index, setModel in VStack(spacing: 8.0) { SetContentView() } } ... } .listStyle(.plain) .buttonStyle(.plain) VStack { WatchRestTimerView(viewModel: viewModel.restTimerViewModel) Spacer() } } .tag(WatchExerciseLoggingTab.logExercise) // HERE IS THE TITLE SET .navigationTitle(viewModel.name) NowPlayingView().tag(WatchExerciseLoggingTab.nowPlaying) } .tabViewStyle(PageTabViewStyle()) .navigationDestination(for: WatchWeightAndSetExerciseSummaryPushedView.self, destination: { _ in RedactedView() }) } } This prevents me from migrating to Xcode 26, I would also appreciate if anyone has a work around until there is a fix for this, I mean I can stop using navigation title and add a Text at the top but it is not quite the same UI experience we get from the navigation title in a watch app.

Hi I developed a music app that plays offline audio and displays lyrics using Live Activities. According to ActivityKit documentation, Live Activities can be updated from the background. However, in my case, updates stop after ~30 seconds when the app goes to the background or the device is locked. Important points: The app continues running in the background (audio playback works fine using AVAudioSession with .playback) Background code execution is working as expected Only the Live Activity stops updating I am not using push updates since this is an offline app. Is there any limitation or requirement for updating Live Activities continuously in the background during audio playback? Audio Session Configuration let session = AVAudioSession.sharedInstance() try session.setCategory( .playback, mode: .default, options: [.mixWithOthers] // ✅ DO NOT interrupt other audio ) try session.setActive(true) print("✅ [AudioSession] Activated with mixWithOthers") } catch { print("❌ [AudioSession] Error: \(error)") } Live Activity Update Methods guard let activity = getLiveActivity(for: recordID) else{ print("⚠️ No Live Activity found for recordID: \(recordID)") return } guard activity.activityState == .active else { print("⚠️ Activity is not active") return } Task { let content = ActivityContent( state: state, staleDate: Date().addingTimeInterval(60 * 60 * 12), relevanceScore: 1.0 ) await activity.update(content) print("✅ Live Activity updated with ActivityContent") } }

I have an app that has suddenly gotten a non-public API error after uploading the archive to TestFlight. The error is posted in full below, and has never occurred before. I'm not using the _UIDeviceOrientationDidChangeNotification symbol but I do have two extensions that use UIDevice.orientationDidChangeNotification. However those extensions are not included in the target for the two watch extensions where the error occurs. Has anyone seen this problem before or have some advice? 90338: Non-public API usage. The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/watchkitappExtensionBeta: _UIDeviceOrientationDidChangeNotification,The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/PlugIns/watchkitappWidgetExtensionBeta.appex/watchkitappWidgetExtensionBeta: _UIDeviceOrientationDidChangeNotification. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Sign-in with Apple suddently broke in my App. The button trigger the system Apple sign in modal, I can sign in without errors but then nothing happens on my App. It seems it never goes in the onCompletion. SignInWithAppleButton( .signIn, onRequest: { }, onCompletion: { // Never get called } ) The button is inside a custom modal.

While I was creating a shortcut using the dictionary function I encountered a bug. When creating a new dictionary to store the date and some other stuff I set a value to the current date variable. I went to change the date format to one I preferred I was unable to access the submenu to do so. To figure out what was going on I did some testing and here is what I found: You can't access the submenu of any inserted variable This only happens in newly created dictionaries You can be fix the dictionary by simply closing and opening the shortcut This bug does not happen on Iphone How to make this bug happen: Open any shortcut Create a new dictionary Add a variable in the value field You can no longer access the sub menu to edit the variable.

Apple has negged my developer account docs for 6 months. How do I get someone on the phone? I had moved the company’s jurisdictions from EU to USA so it is a new Apple Developer account. In truth, I would rather just update my original account to the new company in USA but I can’t do that either.

Problemas com cartoes de crédito onde as operadoras rastreiam e com base …. O Brasil é um país onde organizacoes )) usam e abusam , acesso - cartões bloqueados - inadimplência - trabalho com órgão federal , minha conta , está sendo analisada por fiscais / alguma alternativa que possa colocar cartão de crédito pra não perder meu ( iCloud ) help entre em contato me ajudem como colocar um cartão fiel

I’m looking for guidance on an unresolved Apple Developer Program membership migration. My account is being converted from an individual membership to an organization membership. I have already provided all requested documentation to Apple Developer Support and opened a new case, but the migration remains unresolved. Today I have been on hold for nearly 2 hours. This has blocked our release since April because the account is effectively unable to proceed while the migration is pending. Details: • Migration type: Individual to Organization • Status: still pending • Business impact: production release blocked since April • Documentation already provided: legal entity documentation, D-U-N-S information, and requested verification materials I am not posting private documents here. I’m trying to understand whether there is any additional escalation path or whether Apple staff can confirm the correct team is handling this migration. Has anyone had success getting this unstuck, and is there any Apple process beyond the normal support case flow?

My iPadOS app can open .xml files. In my XMLApp.swift, I hooked up a: var body: some Scene { WindowGroup(id: "main") { .commands CommandGroup(replacing: .newItem) { ... Button(.openDot) { openXMLFile() } ... Next, I entered a new UTImportedTypeDeclarations / UTExportedTypeDeclarations in Project Settings -> Target -> Info -> Document Types, Exported Type Identifiers, Imported Type Identifiers, for the XML file-type: ... <key>UTImportedTypeDeclarations</key> <array> <dict> <key>UTTypeConformsTo</key> <array> <string>public.data</string> <string>public.xml</string> <string>public.content</string> </array> ... As soon as I do that, Xcode creates an additional Open... menu entry all the way at the bottom of the File menu. I cannot get rid of this additional menu entry. Its state is disabled (grayed out). I have my own Open (per the code above), which also responds to ⌘ - O. My menu entry works fine, as long as I disable the same keyboard shortcut so they don't collide. The extra Open entry is also displayed on the matching iPadOS simulator. From the same codebase, the Open is not displayed on the Mac (targeting macOS, not Catalyst). On macOS, only my Open is in the File menu, as expected. Why is there a duplicate Open menu entry and how do I get rid of it?

Hello, I am currently experiencing an issue during the App Review process related to a third-party payment integration using Toss Payments. Our app loads a payment widget from an external script hosted at: https://js.tosspayments.com/v2/standard In our local and production environments, the payment module works without any issues. However, in the App Review environment, the script appears to fail to load or initialize properly, resulting in an "Unknown Error" during payment widget initialization. We suspect that the App Review environment may have network restrictions or firewall rules that block or limit access to this external CDN (AWS-based), preventing the script from being fetched. We have already: Verified that the script loads correctly in all non-review environments Submitted a video demonstrating the normal payment flow Contacted the payment provider, and they confirmed that there are no IP blocks or restrictions on their side My questions are: Does the App Review environment impose restrictions on external CDN domains or third-party scripts? If so, what is the recommended approach for handling payment SDKs that rely on external script loading? As a temporary workaround for review purposes, would it be acceptable to: Bypass the actual payment SDK Replace it with a mock or simplified flow (e.g., tapping the payment button immediately proceeds to a success screen) Restore the real payment integration after approval? We want to ensure compliance with App Store guidelines while also resolving this review-specific issue efficiently. Any guidance or similar experiences would be greatly appreciated. Thank you!

Hi, My app version 1.1.0 has been in ‘Waiting for Review’ for over 2 weeks, this is significantly longer than any previous submission. Could you please check if everything is in order or if any action is needed from my side? Thank you

Hi everyone, We’re facing an issue while trying to change the Primary Language / Primary Locale of a long-standing live iOS app in App Store Connect. The app has been live for 4–6+ years. When attempting to update the Primary Locale from App Information, we receive the following error: “Primary Locale couldn’t be saved because you must first provide all the required screenshots for each version in this language.” However: The target localization (English – UK) already exists. All required screenshot sets are uploaded. No screenshot sections are blank (iPhone and iPad – all visible display sizes). Both the live version and the version in review contain complete screenshot sets. No Apple Watch or iMessage extensions are currently included in the build. A clean build has been uploaded and selected. Removing the version from review does not resolve the issue. There are no visible validation errors in the UI. This appears to be either: A hidden backend validation requirement, A legacy platform association, Or a Primary Locale lock tied to the app’s original configuration. Has anyone successfully changed the Primary Locale for an older live app recently? Is there a known limitation for apps created several years ago? Would appreciate any insight before escalating further. Thanks in advance.

Hello Apple team, We would like to access the user's available purchases from the keyboard extension. Making purchases directly from the keyboard is a great benefit, but we assume it is intentionally disabled to prevent abuse or fraudulent purchase attempts. What we care about the most is determining if the user has an item that contains a discount or a free trial to personalize messaging when we suggest the user go to the app and make a purchase. We hope you'd consider revising your policy around StoreKit usage.

Hi @DTS Engineer 😊 in tvOS 26.5 Beta 2 is still this annoying Shadow Glitch… 😔 I have submitted an Bug-Report, but dont get an Answer… FB20049918 The Animation is not smooth and the Shadow and the Liqud-Glass 3D-Edge is abruptly „jumping“… I don’t get any Response from the Apple Engineers. But this GUI Glitch makes the otherwise very high-quality tvOS GUI appear very unprofessional. Could you please help me? 🤔 Please ask again the Apple Engineers about the current State. Best Regards, Christian 😉