Overview

Hello Apple Developer Community, We are adapting our UIKit-based iOS application for iPhone Duo and have encountered an unexpected layout issue when switching the app language to Arabic. We would appreciate any guidance from Apple engineers or developers who have experience with RTL layout behavior on this device form factor. ### Environment - Device: iPhone Duo Simulator - OS: iOS 27.1 (official release, non-beta) - Xcode: 27.1 (official release, non-beta) - Framework: UIKit - Layout system: Auto Layout - Device system language: English (LTR) - App language: Arabic (RTL) ### Problem Description Our application supports changing the app language independently of the device's system language. When the system language is English and the app language is Arabic, we configure the semantic content attributes of several UIKit classes globally: ```swift let cAttribute: UISemanticContentAttribute = language.isRTL ? .forceRightToLeft : .forceLeftToRight UIView.appearance().semanticContentAttribute = cAttribute UIButton.appearance().semanticContentAttribute = cAttribute UICollectionView.appearance().semanticContentAttribute = cAttribute UITableView.appearance().semanticContentAttribute = cAttribute UITableViewHeaderFooterView.appearance().semanticContentAttribute = cAttribute ``` After applying these settings, we observe a large, unexpected blank area along the left side of the interface on the iPhone Duo simulator. Multiple screens are affected, and views positioned using Auto Layout appear to leave additional space on the left, resembling an unexpected safe-area inset or margin. When the app language is English, the layout behaves as expected. The issue occurs when the app language is Arabic while the device system language remains English. We have not yet determined whether this is related to semantic content attributes, trait propagation, Auto Layout, safe-area behavior, or a device-specific layout consideration. ### Questions 1. Is using `UIAppearance` to set `semanticContentAttribute` globally a recommended approach for app-level RTL language switching in UIKit? 2. Could this configuration affect safe-area insets, layout margins, or Auto Layout behavior on iPhone Duo? 3. Would `traitOverrides.layoutDirection` be a better approach for controlling the layout direction when the app language differs from the system language? 4. If `traitOverrides.layoutDirection` is appropriate, where should it be applied—for example, on the root view controller or a container view controller—to ensure that the intended layout direction propagates correctly to descendant views? 5. Are there any iPhone Duo-specific layout behaviors or known issues that developers should consider when implementing RTL support? 6. What implementation strategy does Apple recommend for supporting in-app language switching between LTR and RTL languages in an existing UIKit application? Our goal is to support Arabic and other RTL languages reliably without introducing unintended spacing or layout changes, while keeping the device's system language unchanged. Any suggestions, documentation references, sample code, or insights into the underlying behavior would be greatly appreciated. Thank you for your time and help! Best regards, iOS Development Team

I would like to identify a supported, minimally scoped diagnostic method for a code-signature verification failure, without changing certificates, trust settings, or system protections. The command execution environment reported macOS 27.0.1, build 26A434. The following command was run against the standard system executable: /usr/bin/codesign --verify --strict --verbose=6 -R '=anchor apple' /usr/bin/printf It returned exit status 1 with: CSSMERR_TP_NOT_TRUSTED In architecture: arm64e.x1 The designated requirement displayed for the file was: identifier "com.apple.printf" and anchor apple The signature display reported Authority=(unavailable). Following TN3161, the CMS data was inspected structurally: it contained three certificate structures, whose recorded validity periods included the observation date. This was not a cryptographic or trust validation, and I do not treat the file as authenticated. My question is how to distinguish a certificate/trust rejection from inability to complete evaluation in the command's execution context. The documentation for SecStaticCodeCheckValidityWithErrors describes detailed errors, and kSecCodeInfoTrust describes access to the trust object used in code-signature evaluation. Is either a supported diagnostic route for this system executable and architecture? If so, please identify the required flags, prerequisites and minimum non-sensitive result fields. In particular, I do not want to change the strict or architecture coverage merely to obtain a passing result. No diagnostic using those APIs has been implemented or run. I am not asking to re-sign the system file, install certificates, reset trust settings, disable protections, or bypass validation. I would prefer an initial diagnostic that does not require private Keychain contents, broad system logs, or a full diagnostic archive. I understand that a diagnostic result or a successful information query would not by itself authorize execution or prove that the environment is safe.

Hello! Our navigation app has the CarPlay Navigation entitlement and uses CPMapTemplate. We want to display a compact current speed indicator and speed limit sign directly on the map, alongside the standard maneuver and ETA templates. The CarPlay Developer Guide says the base view must exclusively draw a map and must not contain custom UI overlays. However, Waze and Google Maps for example both show these indicators and Mapbox’s public CarPlay implementation adds a custom SpeedLimitView to its map view controller. Are these speed indicators permitted as part of the map presentation? If so, what implementation and placement requirements apply if any?

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

Our app Alfa (Apple ID 6755045487), version 1.4.0, build 129, has been in Waiting for Review since 11 October. We requested an expedited review on 16 and 19 October and resubmitted on 20 October, and it has still not been picked up. Our other app on the same account, Alfa Skóli (6804282983), was submitted on 19 October and reviewed within a day. The release has been live on Google Play since 18 October. Support case 103002844967 is open with no reply yet. Is anything holding this submission, or anything needed from us?

Hello, Since I upgraded my iPad (iPad Pro 11" 2nd generation / A12z) to iPadOS 27 I have the following issue with SwiftPlayground. The preview no longer works and gets stuck on "Preview paused / Restart to continue". If I click on the refresh button, the button becomes disabled a few seconds but preview still remains on "Preview paused". It is quite easy to reproduce : Start SwiftPlayground Click "New playground" Click "App" When "My App n" appears on playground browser click on it I already tried to uninstall / reinstall SwiftPlayground and rebooting my iPad but it didn't help. Thanks for any help

Hi! I have been trying for the last two days to join the development program and I keep getting this error after accepting the legal agreement: { "responseId": "a20e6c23-aaeb-440f-998a-d2866b9b6d64", "resultCode": 202018, "resultString": "Your request could not be processed", "userString": "Your request could not be processed", "creationTimestamp": "2026-10-22T14:02:28Z", "userLocale": "en_US", "requestUrl": "https://developer.apple.com/services-enrollment/submitIndividualEnrollment", "httpCode": 406 } I don't know what's wrong nor what I need to do to fix it. Can anybody please help me?

We are developing an Alternative App Marketplace and are in the process of setting up distribution through App Store Connect. For reference: - Team ID: [G2547U6TXN] - Primary Bundle ID: [com.gameloot.ios] - Alternative App Marketplace status: Assigned We have added the "Alternative App Marketplace" capability to our referenced Capabilities, and our Alternative App Marketplace is already in the Assigned state. However, when we use Xcode's Distribute App to upload to App Store Connect, we get an Invalid entitlement error, asking us to remove com.apple.developer.marketplace.app-installation. (See the attached screenshot.) We would like to confirm how to upload our third-party marketplace app to App Store Connect via Xcode. When we upload a public key through the App Store Connect API endpoint https://api.appstoreconnect.apple.com/v1/alternativeDistributionKeys using an Account Holder role, we receive error code 409: "Provider doesn't have marketplace apps."

CalPot App Review Delayed for Over 3 Weeks Despite Multiple Resubmissions and Support Tickets Hi Apple Developer Community, We're experiencing an unusually long delay with our app submission and would appreciate guidance from Apple or other developers who have experienced something similar. Here is the timeline: Initial submission: We submitted our app for review and received feedback identifying an issue within approximately 24–48 hours. Issue resolved: We corrected the reported issue and promptly resubmitted the app. Second review: The submission remained in "waiting for review" for at least two weeks without progressing. Support requests: During this period, we submitted at least three support tickets seeking assistance. Submission cancelled: After the extended delay and unsuccessful attempts to resolve the situation through support, we cancelled the existing submission and submitted it again. Current status: Another week has passed, and the app remains stuck at "Waiting for Review" with no further updates or requests for information. Our concern: We understand that some apps require additional review time. However, the initial review identified an issue within 48 hours, while subsequent submissions have remained pending for weeks despite the issue being corrected. Apple also confirms that "Waiting for Review" means the review has not yet started. Our questions: Is it normal for an app to remain in the review process for this long after an initial issue has been resolved? Could cancelling and resubmitting have caused further delays or restarted the review queue? Is there a way to determine whether our submission is being actively processed or is blocked by an issue that isn't visible in App Store Connect? What is the appropriate escalation process when multiple support tickets have already been submitted without resolving the situation? We would sincerely appreciate any assistance from an Apple representative or developers who have encountered this issue. Thank you in advance.

Hello, I'm requesting a status update on our Apple Developer Program Organization enrollment. Enrollment ID: 7A7WRTQW97 Organization: SWISS KEY TRADING AG (Switzerland, Commercial Register No. CHE-455.888.722) Enrolled as: Organization Applicant role: IT Responsible, enrolling on behalf of the company We initially received a document verification rejection citing (1) a photo ID mismatch and (2) an employment verification letter missing official letterhead and signature. We have since resubmitted corrected documentation addressing both points. The enrollment has been showing "Your enrollment is being processed" since 08.07.26. Could someone let us know if any further information is needed, or confirm expected next steps ? Thanks in advance and have a great day !

Hello Apple App Review Team, I'm seeking urgent assistance with Carrying The Fire (Apple ID: 6820179361), submitted on 9 October 2026, which has now remained in "Waiting for Review" for over eight days, without progressing to active review. An expedited app review request was also submitted. The app is an essential component of a major government-funded public arts event on 7 November 2026 in Albany, Western Australia, involving approximately 2,000 community participants. The event is presented by FORM as part of Albany 2026, with support from the Australian Government's Festivals Australia program and Lotterywest. The performance depends on participants downloading and preparing the app well in advance. Our planned distribution period is already underway, and the continued delay is directly affecting participant preparations and putting the event at risk. The Android version has already been approved and published on Google Play, but iOS participants are currently unable to download or prepare the app, creating an increasingly concerning issue as the event approaches. We have submitted a formal expedited-review request and contacted Apple Developer Support twice (Case ID: 102994798591), but have received no response. Given the fixed event deadline and the significant number of participants affected, could an Apple App Review representative please urgently investigate our submission and escalate it to the appropriate team? Official event information: https://www.albany2026.com.au/events/carrying-the-fire Any help here would be truly appreciated. Thank you for your assistance.

My app has been waiting for review since September 29, 2026 with no updates. I am not getting any response on the Apple Developer Forums or from Apple Support. Please provide clarity on the delay or update the estimated review time on the official website. These extended review times with no clear timeline are costing developers too much.

Hi, I believe I have found a Core Audio regression in macOS 27. This exact hardware configuration worked correctly on macOS 26, and the issue started immediately after upgrading to macOS 27. Hardware: Mac mini M2 2 × MSI MP243X monitors Monitor 1 connected via HDMI Monitor 2 connected via DisplayPort Both monitors expose a 2-channel audio output to macOS On macOS 26: I used Audio MIDI Setup to create a Multi-Output Device containing both MSI MP243X audio outputs. Audio played simultaneously through both monitors without any issues. On macOS 27: Both audio devices are still detected correctly and both work perfectly when selected individually: HDMI only: WORKS DisplayPort only: WORKS HDMI + DisplayPort simultaneously: FAILS This is reproducible even immediately after a full reboot. When I create a new Multi-Output Device containing both MSI outputs and select it as the system output, audio playback cannot start. For example: afplay /System/Library/Sounds/Glass.aiff returns: Error: AudioQueueStart failed ('stop') I captured Core Audio debug logs while reproducing the problem. Core Audio initially reports that StartIO succeeded, but the physical display audio device then fails to establish a timeline. Relevant log messages include: HALS_IOEngine2::_StartIO succeeded Device 3669B540-0000-0000-2623-0104A5351D78 is not running. could not establish a timeline after waiting 10000000 microseconds stopping with error 1937010544 StartIOThread: the IO thread failed to start, Error: 1937010544 I have already tested the following: Both devices at 44.1 kHz / 24-bit Both devices at 48 kHz / 16-bit Recreating the Multi-Output Device from scratch Using the HDMI device as clock source Using the DisplayPort device as clock source Different drift correction configurations Restarting coreaudiod Full macOS reboot Testing both outputs individually immediately after reboot Alternative multi-device audio routing software The behavior is always reproducible. Each MSI MP243X audio endpoint works correctly by itself. The failure only occurs when both HDMI and DisplayPort audio endpoints are opened simultaneously. system_profiler correctly detects both devices at 48 kHz: MSI MP243X Output Channels: 2 Current Sample Rate: 48000 Transport: HDMI MSI MP243X Output Channels: 2 Current Sample Rate: 48000 Transport: DisplayPort This does not appear to be a problem with either monitor or connection individually, because both outputs continue to work independently. The important difference is the macOS version: macOS 26: HDMI + DisplayPort Multi-Output = WORKING macOS 27: HDMI only = WORKING DisplayPort only = WORKING HDMI + DisplayPort Multi-Output = FAILS with AudioQueueStart 'stop' / Core Audio error 1937010544 No hardware, monitor, cable, or connection changes were made between the working macOS 26 configuration and the macOS 27 configuration. This therefore appears to be a regression in the Core Audio/display-audio path introduced with macOS 27 when two display audio endpoints (HDMI + DisplayPort) are opened simultaneously. Has anyone else been able to reproduce this on macOS 27, particularly on Apple Silicon? I can provide the complete coreaudiod logs and run additional Core Audio diagnostics if needed. Additional isolation tests: Both monitors can remain physically connected to the Mac at the same time. With both HDMI and DisplayPort connected: Selecting the HDMI MSI MP243X as the only output works correctly. Selecting the DisplayPort MSI MP243X as the only output works correctly. Opening both audio endpoints simultaneously causes the failure. Therefore, simply having both displays connected does not trigger the issue. The failure appears specifically when Core Audio attempts to run both display-audio endpoints at the same time. I also tested this using third-party multi-device audio routing implementations instead of relying only on Audio MIDI Setup. The same behavior occurs: either MSI MP243X can be opened and used independently, but attempting to route audio to both devices simultaneously fails. This suggests that the issue is below the Multi-Output Device configuration itself and may be related to starting/synchronizing two display-audio IO engines simultaneously. During the failure, the Core Audio log sequence is particularly interesting: The physical device is detected normally. The audio format is configured successfully. Core Audio reports that StartIO succeeded. The device subsequently reports that it is not running. Core Audio waits 10 seconds for a timeline. Timeline establishment fails. The IO thread terminates with error 1937010544 ('stop'). One captured conversion path was: 2 ch, 48000 Hz, Float32, interleaved -> 2 ch, 48000 Hz, Int16, interleaved so both sides were operating at 48 kHz during this test. Another important observation is that restarting coreaudiod does not resolve the simultaneous-output problem. A complete reboot also does not resolve it: immediately after a fresh boot, before launching any third-party audio-routing software, both physical outputs work individually but a newly created Multi-Output Device still reproduces the failure. This makes the issue highly reproducible on this machine. Minimal reproduction: Boot macOS 27 with both MSI MP243X monitors connected. Open Audio MIDI Setup. Verify both MSI MP243X devices work independently. Set both devices to 48,000 Hz. Create a new Multi-Output Device. Select both MSI MP243X devices. Select the new Multi-Output Device as the system audio output. Run: afplay /System/Library/Sounds/Glass.aiff Expected result: The sound is reproduced simultaneously through both monitors, as it was on macOS 26. Actual result: Error: AudioQueueStart failed ('stop') Switching the system output back to either individual MSI MP243X restores audio playback. The problem can then be reproduced again by selecting the Multi-Output Device.

Hello Apple Developer Support / App Review Team, My first iOS app, **PlanB: Dating, Social & Plans**, has remained in Waiting for Review since **October 13, 2026**. Submission ID: **28c83367-dd0b-4a22-b244-149277121d0d** The submission includes the iOS app version and associated in-app purchases and subscriptions. All submitted items continue to show Waiting for Review as of October 23, 2026. I have already submitted an expedited review request through the official portal and raised a support ticket, but I have not received any response or any indication that the review has started. This **delay is blocking the planned launch of my app** which is planned on 27Oct. I understand that review timelines can vary, and I am ready to provide any additional information or resolve any issues immediately. Could you please: - Confirm whether my expedited review request has been received and considered. - Confirm whether any information, agreement, or other requirement is preventing the review from starting. - Escalate the submission for review or advise me on the appropriate next step. I would appreciate any clarification on the status of this submission. Regards, PlanB Developer

Hello Apple team and community, Trying to enroll since July 2026 (original case 20000119049793), actively blocked since early October with “Unable to Continue. Contact support.” No further detail given. Tested across 3 Apple Accounts (one brand new, zero history) and 2 devices (Mac, iPhone) — identical error every time, even after signing the Developer Agreement on one account. I noticed a similar report here (72-day blocked case) where support confirmed this can be caused by a backend flag tied to a trusted phone number being associated with multiple accounts — something only the Operations team can clear, not regular support. This matches our situation: our trusted number has been used across a few recent account attempts while troubleshooting. Could someone from the Operations/Enrollment team please check if this is the cause for Case IDs 102998415457 and 103003885694, and clear the flag if so? This is blocking an active client app launch. Any help greatly appreciated.

Hello App Review Team, Requesting a status check on our first App Store submission from a new developer account. We understand accounts with limited review history take longer, we'd like to confirm the submission is actually queued and that nothing on the account side is holding it. App name: Ayl (submitted as Atlys Voyager, renamed Oct 1) Apple ID: 6817770880 Developer account: Atlys, Inc. Platform / version: iOS 1.0.0, build 6 Current submission ID: f60cdaaba-251b-4dd4-a0f0-754f110805bf Current status: Waiting for Review since Oct 13 Expedited review requested: Oct 13, no response Developer Support case: 103001953476 Timeline: Oct 1: Rejected under 2.1 (Information Needed, new account). Added the requested walkthrough video, app description, setup instructions, external services and regional details to the Notes field. Oct 12: Reviewed (submission 3f51e4db-b7d2-4594-8371-3b45f41cfc9e). Two issues: 5.1.1(ii) location purpose string, 2.5.4 background audio mode. Oct 13: Resubmitted build 6. The location purpose string now states the specific use (showing must-visit places near the user); the audio background mode has been removed from Info.plist. Both changes and a video of the location feature are documented in the Notes field. Oct 18: Build 10 of 1.0.0 passed Beta App Review and is live with external TestFlight testers. If anything further is required from us: documentation, credentials, or clarification, we will respond the same day. Thank you

Both of our first-ever submissions from a new organization account have stayed in “Waiting for Review” and have never moved to “In Review”. First app (iOS 1.0), submitted Oct 9, 2026, waiting 12 days Second app (iOS 1.0.0), submitted Oct 14, 2026, waiting 7 days Already checked: Free and Paid Apps agreements, tax forms, bank account, and DSA compliance are all Active No messages in App Review or the Resolution Center No cancel or resubmit on either submission I opened a support case on Oct 17, 2026 and have received only the automatic confirmation. Apple’s published target is 90% of submissions reviewed in under 24 hours, so I’d like to know whether both submissions are correctly queued or whether there is an issue on the account. Much appreciated thanks.

Hello, Does converting my existing individual account to an organization keep my existing Team ID? Will my existing Developer ID Application certificate be revoked? I've seen other answers to these questions on the forums, but not officially answered by an Apple employee, and a couple of the answers were ambiguous. Thank you, Eric

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,

This situation is odd for me. I've been running another app on this Apple developer account since May, all new submissions for review are usually within 24 hours and even the first initial review took 3 days. I've recently submitted a new app for review that has now been in review for over 2 weeks but the problem i'm having is the app is already live on the play store with over 15,000 users (social media blew up) and i'm stuck here not knowing what the timeline is for release on iOS (and over 22,000 on an email waitlist for iOS). I'm not here to brag numbers but when Apple says they need a reason for expedited review... this is it. Anyone have any tips? i.e. ways to contact the Apple review team? I've tried emailing but no luck as of yet.