Is there a process or Apple contact for requesting expedited review of In-App Event assets? My major update with iPhone Duo support is already approved and live, but the associated In-App Event and creative assets are still pending review. I know it’s the weekend, but I’m hoping to have the event live by Tuesday, October 27, at 9 AM PDT, to coincide with the launch. Thank you so much!

Hello everyone, I'm looking for advice regarding my Apple Developer account. My account was suddenly terminated by Apple, even though I have never knowingly violated any Apple Developer Program policies. None of my apps had been rejected for fraud or policy violations, and I never received any prior warning or notice about suspicious activity. The only explanation I received from Apple was: "Apple has good reason to believe that you violated Section 3.2(f) due to documented indications of fraudulent conduct associated with your account." However, Apple did not explain what specific activity or evidence led to this conclusion. Has anyone experienced a similar situation? Is there any realistic chance of getting a terminated developer account reinstated after an appeal? Also, does Apple ever provide more detailed information about the reason for termination, or do they usually keep the explanation general? I would appreciate any advice or shared experiences. Thank you.

Hello, I’m trying to complete the W-8BEN tax form in App Store Connect, but the Country/Region field is locked and automatically filled with the wrong country. I am an Israeli citizen and a tax resident in Georgia, where I have permanent residence and a registered individual entrepreneur. The form currently shows an incorrect country, and I have no option to edit it. I have already contacted Apple Developer Support about this issue and was advised to contact the Finance/Tax team, but I have not been able to get the issue resolved. Could someone please advise: How can I correct the Country/Region field in the W-8BEN form? Can Apple Finance/Tax Support unlock or reset the form so that I can enter the correct information? Is there another way to submit the W-8BEN if the field remains locked? I would appreciate any guidance from someone who has experienced the same issue. Thank you.

I'm posting here after 8 months of back-and-forth with Developer Support (case 102685152651) because I've exhausted that channel and need to know if others have experienced this or if any Apple engineers can advise. The issue: When a user types "Dabah" — the exact name of my app — the App Store autocorrects/redirects to "Sabah." My app does not appear in those results. It only appears when the user searches "Dabah recipes." This means users who know the app by name cannot find it unless they add a secondary keyword. What makes this clearly a system-level bug, not a ranking issue: The same behavior occurs inside Apple's own Developer Marketing Tools portal. Searching "Dabah" returns only Sabah-related apps. Searching "Dabah recipes" finds my app immediately. This is not a user-facing algorithm issue — it's happening in an internal Apple tool. "Dabah" is a unique, uncommon word with no major competing apps. There is no legitimate reason an exact-name search should be overridden. The app has been live on the App Store since mid-2024, is properly indexed (it surfaces on keyword searches), and has "Dabah" listed as a keyword. The problem is specifically in the autocorrect/normalization layer treating "Dabah" as a misspelling of "Sabah." I've submitted screen recordings demonstrating both behaviors. Developer Support has confirmed my ticket is with the engineering team, but I've received no resolution or timeline in 8 months. Has anyone else encountered autocorrect overriding an exact app name match? Is there a known path to escalate search indexing bugs beyond the standard Developer Support channel? App: Dabah (id6745241806) Category: Food & Drink

Hello, my app "YOGO Loops" (Apple ID: 6799279746) has been approved and is "Ready for Distribution", but it is unavailable in all 27 EU countries. App Store Connect > Business > Compliance shows: Digital Services Act | 27 countries or regions | Last Updated: 11 Aug 2026 | Status: In Review Pricing and Availability shows "Trader status not provided" / "Cannot sell" for all EU territories. Everything else is Active: Tax forms (W-8BEN): Active Administrative Cooperation Directive (7th amendment): Enabled Trader information (address, phone, email): submitted I am an individual developer based in Germany, so my main market is completely blocked. Apple states a review time of about 5 business days, I am now at day 38. I have already filed a support request with Apple. Has anyone had a DSA verification unstuck after a delay like this? Is there an escalation path beyond the standard support form? Thank you.

Hello, I’m experiencing a situation with my app Waspp that I’m trying to understand. The app was approved by App Review on Feb 24, 2026 and is currently available on the App Store in the United States. However, distribution in the European Union (Belgium and France) is blocked due to the Digital Services Act (DSA) trader verification, which still shows “In Review” in App Store Connect. Some details: App Review completed: Feb 24 DSA compliance submitted: Feb 25 Status: Still “In Review” after more than two weeks Documents requested by Apple Support have already been uploaded via their secure link App availability shows “Cannot Sell” for Belgium and France The app is live and downloadable in the US Because of this, the launch of the app in the EU is currently blocked even though the app itself has been approved. My questions: Is it normal for the DSA trader verification to take this long? Has anyone experienced a similar delay with EU distribution? Is there anything else that can be done from the developer side to unblock the verification? Any feedback or similar experiences would be greatly appreciated. Thanks!

Hi I have an app in App store with name App1 with bundleID bundleID1. As a part of upgrade I want to change the name of the app to App2. I use the same bundleID1. My new install via test flight shows the new app name App2. But the upgrade via test flight shows the old app name(App1). The Finder, spotlight and dock shows the old appname. I want the Finder, spotlight and dock to show the new app name(App2). What should I do for that? I have updated CFBundleDisplayName and CFBundleName to new app name(App2). Thanks

Hello Apple Developer Community, I hope this message finds you well. I recently submitted an astrology-related app to the App Store, and it was rejected with the following reason: "Your app primarily features astrology, horoscopes, palm reading, fortune telling, or zodiac reports. As such, it duplicates the content and functionality of many other similar apps currently available on the App Store." I would like to seek some clarification and guidance on how to address this issue and bring my app in compliance with Apple's guidelines. I understand that there are similar apps available, but I believe my app offers unique and valuable features that differentiate it from others. Specifically, I would like to know: What criteria does Apple use to determine whether an app is considered duplicative of others in the same category? Are there any specific guidelines or best practices to follow when submitting astrology or similar apps to ensure they are approved? Is there a way to highlight the distinctive features of my app that make it unique and provide a better user experience compared to other similar apps? Are there any precedents or examples of successful astrology apps that were approved on the App Store, and if so, what factors contributed to their approval? I want to ensure that my app complies with Apple's policies and provides value to users while avoiding any issues related to duplication. Any insights or guidance on this matter would be greatly appreciated. Thank you for your time and assistance. Best regards,

My app "Haniva: Text zu Handschrift" (Apple ID 6812813987) launched on Oct 12, 2026 in Germany, Austria and Switzerland. At launch it appeared when searching for its name "haniva". Since around Oct 16 the App Store rewrites the query: Germany: "haniva" only shows "hanova WOHNEN GmbH" Austria/Switzerland: "haniva" shows apps about "Hannibal" My app does not appear at all. "haniva app" and "haniva handschrift" return it as the first or only result, and the iTunes Search API ranks it #1 for "haniva". It also happens on apps.apple.com, so it is not device autocorrect. Search downloads dropped from 2,831 (Oct 14) to 37 (Oct 17). People who hear about the app on TikTok cannot find it. Developer Support cases: 102999695354, 103004855609, 103004860923. Feedback: FB25285176. Has anyone had this and gotten the spelling correction fixed?

Hello there, I am wondering if I am the only one who does not understand the provided templates for header and search results. Why is there so much blank space and a small art save area? What final format am I supposed to export? First I thought its a broken file and downloaded the figma version but its the same. Can anyboy enlighten me? What am I missing? I'd love to use the new option for headers and search results but am stuck. Thanks in advance!

I'm an independent developer and one of my apps has been stuck in App Review / DSA review for more than 2 months now. I fully understand that reviews take time, especially with the new Digital Services Act (DSA) requirements in the EU, but two months with almost no feedback is honestly frustrating. I've already submitted everything required for compliance and responded to the few messages I received, but the app is still sitting in review without any clear timeline. For indie developers this kind of delay can be really difficult since launches, updates, and marketing plans depend on getting the app approved. Has anyone else experienced very long DSA-related reviews recently?

My update for Mktbox: Stock & Portfolio App (Apple ID: 1237897006, version 27.0) was approved and has been in “Ready for Distribution” since [October 11], with automatic release enabled. The App Store still shows the previous version on all devices I’ve checked. What I’ve verified: Release is set to automatic, with no scheduled date Agreements, Tax, and Banking are all active Pricing and Availability is unchanged I opened support case 102994667282 a few days ago and followed up, but haven’t had a reply. The contact form only offers email for this topic. Could someone from the App Store Connect team look into the release status? Any pointers from others who’ve hit this recently are also appreciated.

I first submitted my Apple Developer Program organization enrollment on 25 September 2026, 26 days ago. I'm now stuck in a loop between Developer Support, payment and identity verification, and I'd appreciate any guidance. Timeline: I enrolled my U.S. LLC in the Apple Developer Program on 25 September 2026. Apple Developer Support asked for identity and business documents. I sent them by email through the manual verification process. My organization enrollment was approved. When I tried to pay the $99 membership fee, the payment failed. I tried several Visa and Mastercard cards, both U.S. and non-U.S. I contacted the banks that issued the cards. They confirmed they never received an authorization request from Apple for any of these attempts. Developer Support then told me to restart enrollment through the Apple Developer app. In the Developer app, I'm now stuck at identity verification. I can't get past it to choose between Individual and Organization enrollment. I'm using a valid passport, but the app never completes identity verification. Support asked for screenshots and screen recordings of the problem. I sent them, but I haven't had a meaningful update since. What confuses me most is that my identity and organization documents had already been verified manually before I was sent to the Developer app. What I'm asking for I'm not asking to bypass Apple's verification requirements. I'm asking whether Developer Support can either: move my enrollment back to the manual identity verification process that already worked, or manually review why identity verification is failing in the Developer app. My existing support case has stopped responding, even though I've followed up. If someone from Apple Developer Support sees this, I'd be very grateful if you could look into it, or tell me how to get the enrollment escalated to the right enrollment or identity verification team. I can share my Enrollment ID, support case numbers, Feedback Assistant ID and other account details privately. Thank you.

our app is in review for over 2wks with no updates. it would be great to at least get some information for apple as to why the extensice delay and an better approx time frame

Is Apple still processing and accepting feature nominations for Duo support/major updates? Thank you. I think I have a meaninful capability with my new build which includes dramatic iPhone Duo use case. Since I cannot record on iPhone duo does editorial have ability to install and use the apps when they right up a feature?

Hi, My W-8BEN form in App Store Connect has “Country or Region of Citizenship” locked to an incorrect value, and I cannot edit it. I need this field corrected so I can submit an accurate W-8BEN. This has been blocking my Paid Apps Agreement for over two weeks. No one replies! Can Apple reset or correct this locked citizenship field? Existing Apple Support Case ID: 21732100. Thanks.

After updating to watchOS 27, some users of my app can no longer launch the watch app. The watch shows: "[App] Needs to Be Updated — The developer of this app needs to update it to work with watchOS 27." The shipping version is not the problem. My current App Store release contains both arm64_32 and arm64 slices in the watch app and its extension, and launches correctly on watchOS 27 when freshly installed. Affected users already have the current version on iPhone. Archives going back to December 2022 also contain arm64. The fix, in both cases so far, is for the user to remove and reinstall the watch app: Watch.app → My Watch → [app] → toggle "Show App on Apple Watch" off, wait for the icon to disappear, then back on. After that it launches normally on the same device and OS version. My working theory is that the installed copy is thinned at install time. A watch that installed the app under an earlier watchOS received an arm64_32-only copy, which persisted through later app updates and OS updates. watchOS 27's 64-bit requirement then rejects it. A reinstall on 27 pulls the arm64 slice. One affected user has had the app installed on an Ultra 2 since December 2023, which fits. I have not been able to verify the contents of the installed copy on a user device, so this is inference rather than confirmed. Two things I'd like to know: Is anyone else seeing this? If so, what was the install history of the affected devices? Is there any supported way to force a watch app to be re-downloaded, or to detect from the iPhone app that the watch copy is in this state? Right now users have no indication that a reinstall fixes it, and the message points at the developer. Feedback filed as FB24834097

Hi everyone, Our app was recently removed from the App Store under Section 3.2 and Guideline 5.6. We believe this decision was unjustified, and we are still waiting for a response to our appeal. We had some technical issues affecting the app's functionality, but we were actively working on a fix. We have now identified a solution and are implementing it, and we were ready to submit an updated build. We understand that apps must comply with Apple's guidelines and provide a reliable user experience. However, we are struggling to understand why the app was removed before we had a reasonable opportunity to fix the technical issues, especially since we did not engage in any fraudulent activity. Has anyone experienced a similar situation? Is immediate app removal a common outcome in cases involving technical issues, and were you able to get your app reinstated after appealing? Any advice or shared experiences would be greatly appreciated.

Since our 1.3.20 update reached users on Sept 11, 2026, a handful of devices terminate at launch right after the App Store auto-update. Restarting the device does not help; deleting the app and reinstalling it from the App Store does. Filed as FB24755993 with 9 crash reports, the delivered package's SC_Info/Manifest.plist and a per-binary fingerprint. What the crash reports say (all identical) Exception Type: EXC_CRASH (SIGABRT) Termination: namespace DYLD, code 1, "Library missing" (terminated at launch; ignore backtrace) Library not loaded: @rpath/FBSDKCoreKit.framework/FBSDKCoreKit Referenced from: <DDB434B7-...> /Volumes/VOLUME/*/Runner.app/Runner Reason: tried: '/private/var/containers/Bundle/Application/<UUID>/Runner.app/Frameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (could not register fairplay decryption, mremap_encrypted() => -1) Backtrace: dyld4::prepare -> dyld4::halt -> abort_with_payload Devices so far: iPhone XR / iOS 18.7.10 (22H374), iPhone 16 / iOS 26.6, iPhone 16 / iOS 18.7.7, plus one more not yet identified. The same package launches normally on the large majority of the ~12,000 devices that updated that day. Delivered Info.plist: DTAppStoreToolsBuild 27A261, DTXcodeBuild 17F113, MinimumOSVersion 15.0. What we established The main executable decrypts fine (dyld reaches dyld4::prepare); the failure is on the first @rpath framework in the load order, which is also the first FairPlay-encrypted embedded binary. It is not specific to the Facebook SDK. The package Apple delivers (pulled with Apple Configurator) is structurally consistent: every binary with LC_ENCRYPTION_INFO_64 has cryptid 1 and SC_Info/<name>.supp/.supf/.supx/.v4.supp/.v5.supf (main executable, App, Flutter, FBSDKCoreKit, FBAEMKit, FBSDKCoreKit_Basics, objective_c, sqlite3, the widget appex); the Firebase/Google frameworks are cryptid 0. SC_Info/Manifest.plist has SinfPaths = [SC_Info/Runner.sinf] and SinfReplicationPaths for all 12 binaries. Only the main Runner.sinf ships; the framework-level .sinf files have to be produced at install time from SinfReplicationPaths. The symptom looks like that replication not being applied to the frameworks after the delta update on the affected devices, while a fresh full install performs it. Nothing in our bundle changed between 1.3.19 and 1.3.20 except Dart code (App.framework): same Xcode 26.6 (17F113), same Flutter engine, byte-identical Facebook SDK 18.1.1 binaries (the only fat arm64+arm64e binaries in the bundle), same Firebase SDK. Both versions run normally from TestFlight and Xcode. The 1.3.20 encrypted variant carries SC_Info timestamps about 18 h after Ready for Sale, coinciding with the start of the auto-update wave. We could not obtain the delivered 1.3.19 package for comparison. Questions Has anyone seen this class of failure since early September, or with packages processed by DTAppStoreToolsBuild 27A261? Is there anything about a bundle (fat arm64+arm64e embedded frameworks? many encrypted frameworks?) that makes the framework .sinf replication on the delta-update path fragile? Is there any developer-side mitigation other than telling users to delete and reinstall? The closest earlier report I found is thread 718950 (2022, iOS 15.7–16.1, ~1 in 200 installs, "reinstall fixes it"); this looks like the same failure but concentrated on one update. fingerprint-1.3.20.json

My October 1, 2026 App Store payout is still missing, despite App Store Connect marking it as Paid. I opened a case with Apple Media Services Finance Support on October 6. The automated acknowledgment stated that my request had been received and allocated, but after multiple follow-up emails over the past two weeks, I have yet to receive a substantive response. My bank has checked twice and confirmed that it cannot locate the incoming payment. It requires transfer confirmation or tracing details from Apple before it can investigate further. I've continued replying to the original support thread, including another follow-up today, October 20, but have received no meaningful update. Has anyone else experienced this recently, and is there an official escalation route for unresolved App Store payout cases when Finance Support does not respond? I'm not looking to open duplicate cases unnecessarily.