Hi, Is it no longer possible to take a screenshot with rounded corners? In Xcode 26, you could hold down the Option key to access a different screenshot menu. This no longer works—neither via the new print button in the Device Hub nor through the command-line tool devicectl. xcrun continues to work, but—once again—there are no rounded corners. Are rounded corners no longer in fashion for screenshots? Christian

I have a powerful machine (Mac Studio M1 Max, 64 GB). Switching between apps is instantaneous. Except for Xcode. It consistently takes 2+ seconds to switch to Xcode from any app under any memory pressure. (And yes, it's an absolutely enormous amount of time for this task.) The same problem was with Xcode 26. I hoped that Xcode 27 will fix it, but nothing changed after updating. There are days when I need to switch between other apps and Xcode often AND many times (in hundreds). This annoying delay is absolutely unacceptable. I'm using Xcode since version 2 and have never experienced this problem. I wonder if other Xcode users experience the same? WHY there's even a delay? Again, no other app behaves like this - and I have quite a few apps open, including multiple heavy Adobe apps. FB25437949

Switched to Xcode 27.2 and it started downloading documentation. After download is finished documentation window is empty, prompting to look up documenation online or download it. Triggering any download does not help – no documentation is available. (Sidenote: Reinstalled Xcode 27.2 and documentation was there. But Xcode started a download automatically and without confirmation and afterwards it is gone)

If you need help investigating a crash, please include a crash report in your post. To smooth things along, follow these guidelines: For information on how to get a crash report, see Acquiring crash reports and diagnostic logs. Include the whole crash report as a text attachment (click the paperclip icon at the bottom of the editor). This avoids clogging up the timeline while also preserving the wealth of information in the crash report. If you’re not able to post your crash report as an attachment, see Can’t Post Crash Report as Attachment below. If you want to highlight a section of the report, include it in the main body of your post. Put the snippet in a code block so that it renders nicely. To create a code block, add a delimiter line containing triple backquotes before and after the block, or just click the Code Block button. If possible, post an Apple crash report. Third-party crash reporters are often missing critical information and have general reliability problems (for an explanation as to why, see Implementing Your Own Crash Reporter). Symbolicate your crash report before posting it. For information on how to do this, see Adding identifiable symbol names to a crash report. If you need to redact the crash report, do so consistently. Imagine you’re building the WaffleVarnish app whose bundle ID is com.example.wafflevarnish but you want to keep your new waffle varnishing technology secret. Replace WaffleVarnish with WwwwwwVvvvvvv and com.example.wafflevarnish with com.eeeeeee.wwwwwwvvvvvvv. This keeps the text in the crash report aligned while making it possible to distinguish the human-readible name of the app (WaffleVarnish) from the bundle ID (com.example.wafflevarnish). Finally, for information on how to use a crash report to debug your own problems, see Diagnosing issues using crash reports and device logs. Can’t Post Crash Report as Attachment Crash reports have two common extensions: .crash and .ips. If you have an .ips file, please post that [1]. The forums let you attach a .crash file but not an .ips file (r. 117468172). To work around this, change the extension to .txt. If the forums complain that your crash report “contains sensitive language”, leave it out of your initial post and attach it to a reply. That often avoids this roadblock. If you still can’t post your crash report, upload it to a file sharing service and include the URL in your post. Post the URL in the clear, per tip 14 in Quinn’s Top Ten DevForums Tips. Getting a Crash Report from the Xcode Organiser The Xcode organiser shows crash reports from customers. If you’re investigating such a crash and want to post a crash report: Navigate to the crash in the Xcode organiser. If you can’t see the right crash, check the filter popups at the top. In the list of crashes, secondary click on your crash and choose Show in Finder. That reveals the Xcode crashpoint document (.xccrashpoint) in the Finder. Secondary click on that and choose Show Package Contents. In the resulting Finder window, find a crash report (.crash) that accurately represents the crash you’re investigating and attach that to your forums post. Share and Enjoy—Quinn “The Eskimo!” @ Developer Technical Support @ Applelet myEmail = "eskimo" + "1" + "@" + "apple.com" [1] Because it’s easy to go from an .ips file to a .crash file. I usually do this by choosing File > Quick Look in the Finder. For more info about these file formats, see this post. Revision History: 2026-11-10 Updated the text that describes the attachment button to account for changes to the forums platform. Made other minor editorial changes. 2025-08-29 Added the Getting a Crash Report from the Xcode Organiser section. 2024-11-21 Added a recommendation to post the .ips format if possible. 2024-05-21 Added some advice regarding the “contains sensitive language” message. 2023-10-25 Added the Can’t Post Crash Report as Attachment section. Made other minor editorial changes. 2021-08-26 First posted.

Each time I launch a Debug version of the app on iOS Simulator, I see the Launch Screen presented and then about a 30-second delay before the app is responsive and debug output appears in the console panel. Filed FB22345091

Anyone working with the 27.3 devices beta in Xcode 27.3 on macOS 27.3? Canvas and device hub/simulator are throwing this error while open, several on first load, then periodically (not sure of the periodicity). Any help is appreciated. Not sure if it's impacting at the code or app, but it is interfering with active work (it assumes modal position while working). Can reproduce from Device Hub only (all other apps, including XCode closed), screencast here - demos 27.2 for the time it is started no errors, 27.3 as soon as it is started "identityservicesd quit unexpectedly" errors. Looks like stages in the rendering also - noticed dock not displayed, error, then dock displayed, next - home icons not displayed, error, then home icons displayed, etc. https://app.screencast.com/iK0BaVIVpjt0O

Hello, I'm having an issue with SwiftUI Preview in Xcode. When I switch between different iPhone models, including iPhone 18 Pro, iPhone 18 Pro Max, iPhone Air, and iPhone Duo, the selected device name changes, but the actual device appearance and preview dimensions remain exactly the same. This happens in all SwiftUI projects, including newly created ones. I've tried reinstalling Xcode, clearing DerivedData and caches, and even performing a clean macOS installation, but the issue still persists. - macOS 27.0.1 - Xcode 27.2 Has anyone experienced this issue or found a solution? Thank you!

As the title reads, is a short and simple issue which is simply very frustrating. Once you exist fullscreen it works, Validate can be pressed in fullscreen, but not Distribute on an archived product.

I am writing this post while I wait for the progress to move from 0% to 3%. Did someone find a way to speed this up? It is a nightmare experience that Apple provides to developers aiming at Watch.

Hello! I'm glad that Xcode 27.2 could fix many StoreKit testing issues (27.2 release notes). While refreshing my unit tests for Xcode 27.2, I noticed a new behavior of "Ask to Buy" transactions. Since Xcode/iOS 27.2 at least, it seems that declining an Ask to Buy request in an SKTestSession makes StoreKit 2 record a purchase. Is this the intended new behavior? To reproduce: let session = try SKTestSession(configurationFileNamed: "ConfigFile") session.askToBuyEnabled = true session.resetToDefaultState() session.disableDialogs = true session.clearTransactions() let result = try await product.purchase() // .pending let pending = session.allTransactions().first! // state .deferred try session.declineAskToBuyTransaction(identifier: pending.identifier) // a few seconds later for await t in Transaction.all { print(t.unsafePayloadValue) }In my case the purchased product is an auto-renewable subscription with a free-trial intro offer, from a local .storekit file, in a unit test run inside a host app. After the decline, I could observe the following iOS 26.2 simulator SKTestTransaction.state = .deferred Transaction.updates : nothing Transaction.all : empty iOS 27.2 simulator SKTestTransaction.state = .failed Transaction.updates : emits a transaction Transaction.all : 1 transaction: ownershipType = .purchased, reason = .purchase, no revocation, expires at the end of the trial. The test session marks the request as failed, yet StoreKit 2 reports an active subscription... My understanding was that a declined "Ask to Buy" request never produces a transaction. With the new behavior, apps relying on Transaction.all or currentEntitlements would grant access that the Apple user refused... Is the new behavior expected? Or is it a regression (and is it limited to SKTestSession) ? Thanks for your help!

My boss received an email from apple to submit an important document needed for your program enrollment, that is "Request for Enrollment Documents". Can any one explain what are the documents we have to submit.

I am getting an error whenever I try get a screenshot from the iPhone DUO in the Device Hub. Error is: "Cannot choose between 2 displays."

Hello, Turning on iCloud Drive sync does not work in iOS 27 simulators. When I sign into an iCloud account and try to enable it by tapping the switch in the iCloud Drive settings within the iCloud account area of Settings, the switch doesn't stay on and the feature is never enabled. I don't get an error or anything telling me what's going on. Anyone else seeing this? When I create a new simulator for iPhone 26.5 it seems to work fine just as before. I've tested this with Xcode 26.6 17F113 and Xcode 27 RC 27A266a.

Tried three times now and absolutely cannot get Xcode 27 to install iOS 27 Simulators. I have done a complete uninstall of Xcode (including things in ~/Library). And even purged /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/ When Xcode 27 (27A266a; release version) is installed and run the first time, I'm greeted with the SDK screen. I select iOS and it downloads that runtime. I can see it in Xcode's Components panel in Settings. I only see Any iOS Device as a target device in Xcode. If I launch Device Hub, it's empty and I cannot add any devices since the Add dialog shows No Runtimes Available. Selecting "Add Platforms in Xcode" takes me back to Xcode, but I only ever see iOS 26.5 or older in the list. I've even tried the various xcrun simctl commands, but to no avail. Why is it so difficult to have a clean install of Xcode 27, have it install the iOS 27 SDK and then be able to build and run existing projects? I'm on the release version of macOS 27.0.1 though the problems persisted earlier today on macOS 27.0 as well.

i have a macbook pro late 2019 and has stopped take any major update software like mac os 27 i had the version of xcode 26.5 which by the way it was crashing many time before the update that it get today the version 27.2 and it says that it can't be opened because it doesn't support this mac ,my question is what should i do ,i get a new one which i can't financialy or there are any updates that i can update the app and worked just fine and be compatible. For me it's not right to disable apps just because there is a new software version and apple can't supported anymore there rest of us what do we do we become thieves.

I'm a paid Apple Developer Program member. Apple Developer Support confirmed by phone that my account has no restrictions, but every development-signed app I install on my registered iPhone is rejected. Environment iPhone 17 Pro,1, iOS 27.0 (24A435), Developer Mode enabled Device registered and enabled in Certificates, Identifiers & Profiles Signed with Apple Development certificates (issuer: WWDR G3), iOS App Development profiles Error ApplicationVerificationFailed 0xe8008018: The identity used to sign the executable is no longer valid.On the device: "This app was not installed because its integrity could not be verified." Device log during installation installd(libmis): Performing online authorization. online-auth-agent: The server returned: {"actions":["REJECT_PROFILE"],"authorized":false,...} online-auth-agent: Permanently rejected profile: <hash, <profile UUID installd(libmis): No online authorization (0x2) installd(libmis): validation failed because of failing online authorization (-402620392)What I've ruled out Not certificate revocation: trustd reports OCSP status revoked=0 definitive=1 for the whole chain. Not app-specific: a brand-new, empty test app with a newly created App ID and a newly created development profile fails identically. Not certificate-specific: same result with two different Apple Development certificates, each in its own freshly generated profile (three profiles in total, all rejected). The provisioning profiles contain the device UDID and the signing certificate, and the app's entitlements are a subset of the profile's. Questions Under what conditions does the online authorization service return REJECT_PROFILE / authorized:false for a paid team whose account shows no restrictions? Is this a known issue with iOS 27 and development profiles? Since the device marks each profile as "permanently rejected", how can I restore authorization for my team on this device once the cause is fixed?

I have encountered a possible compatibility issue with apps built using Xcode 27.1 and running on iOS 15.8 devices. Development environment Xcode 27.1 macOS 27.2 Build Configuration: Debug iOS Deployment Target: 15.8 Test device iPhone 7 iOS 15.8 Observed behavior When running an app built with Xcode 27.1 on an iPhone 7 running iOS 15.8, button interactions sometimes fail to update the user interface. The button press animation is displayed, indicating that the button is being interacted with. However, the expected UI state changes are sometimes not reflected, even after repeated taps. This behavior affects multiple buttons, rather than a single specific button. Comparison An IPA built with Xcode 26.2 works correctly on the same iPhone 7. An IPA built with Xcode 27.1 exhibits the UI update problem. The app runs correctly in the Xcode 27.1 Simulator. Question Is there a known compatibility issue in Xcode 27.1, its Swift compiler, or the iOS SDK that could cause SwiftUI UI updates to fail on iOS 15 devices? Although iOS 15.8 is available as a deployment target, I would like to know whether apps built with Xcode 27.1 are expected to work correctly on iOS 15 devices. Has anyone encountered similar behavior?

在通用架构版本 Xcode 26.3 中，在 Storyboard/Xib、表情键盘和配套的模拟器 iOS 26.2 (23C57) SDK + iOS 26.3.1 (23D8133) Simulator 中存在BUG，无法显示 emoji 表情图案。 虽然现在已经有了更新版本，但是 Xcode 26.3 是 macOS Sequoia 最后支持的版本，也就是有一批设备无法更新 Xcode 软件，只能使用 Xcode 26.3 版本，所以请求官方能修复此问题。 由于更新策略，2019年的苹果电脑最高只能升级到 macOS Sequoia 系统。 从控制台日志来看，不能显示 emoji 表情的 BUG 仅仅是因为缺少 AppleColorEmoji.ttc 和 hapticpatternlibrary.plist 文件。看上去是模拟器的问题，仅更新模拟器镜像文件应该就能修复吧。 FontParser could not open filePath /Library/Developer/CoreSimulator/Volumes/iOS_23D8133/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.3.simruntime/Contents/Resources/RuntimeRoot/System/Library/Fonts/Core/AppleColorEmoji.ttc: [2: No such file or directory] <_UIKBFeedbackGenerator: 0x60000351f700>: Error creating CHHapticPattern: Error Domain=NSCocoaErrorDomain Code=260 "未能打开文件“hapticpatternlibrary.plist”，因为它不存在。" UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000d29bc0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

On Xcode 27 with macOS 27.0.1, I observed Xcode marking an existing project as locked because its file supposedly did not exist. The project used the traditional project.pbxproj format. That file existed, parsed successfully, was readable, and had no filesystem lock flags. Command-line builds succeeded, but the editor continued to show the lock warning. Selecting Unlock produced this error: The file “project.xcproj” could not be unlocked. Could not find the file. There was no project.xcproj in that PBX-format project. A separate minimal iOS project also reproduced the same missing-file lock warning. That sample contains one application target, a minimal Swift source file, and signing disabled. This reproduction suggests the warning is not specific to the main application's source or extensions. These observations were recorded on 10 October 2026. I have not retested the sample today. Apple Developer Technical Support directed me to post the issue here. Is this a known project-lock tracking issue involving the alternative project filenames? What supported diagnostic evidence would help establish why Xcode reports the project as locked, and is there a supported workaround that preserves the existing project format? A standalone reproduction was prepared during the investigation. I can arrange to share it after checking the files for public release.

Hello, I'm facing an issue with the Xcode Canvas preview (#Preview). ​No matter which device model I select from the destination list (e.g., switching between iPhone 11 Pro, iPhone 16, or iPhone 18 Pro Max), the preview rendering remains completely identical. It shows the exact same physical frame (with a Dynamic Island) and the layout dimensions don't adjust to reflect the different screen sizes or notch styles of older devices.