Hello, It seems Xcode 26 beta is lagging the OS releases, which is fine. However, how does one install a Beta N + 1 or N + 2 SDK into the older Xcode beta? I'd like to use iOS 26 Beta 8 from the Xcode 26 Beta 6 install I have. I have tried Settings/Components and Devices & Simulators but nothing Beta 7 nor 8 shows up there. Thanks! -- Greg Bolsinga
Search results for
xcode github
92,015 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello. This issue has been improved in Xcode beta6. Thank you very much.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Below is an English version of your post, ready to copy-and-paste into the Apple Developer Forums: I’m seeing a crash in Xcode 26 beta 3 whenever the StoreKit symbol SKStoreProductParameterAdNetworkSourceIdentifier is present while running on an iOS 15 simulator. Steps to reproduce Install Xcode 26 beta 3. Create any iOS app and run it on an iOS 15 simulator (device model doesn’t matter). Add the following code anywhere and run: override func viewDidLoad() { super.viewDidLoad() if #available(iOS 16.1, *) { print(SKStoreProductParameterAdNetworkSourceIdentifier: (SKStoreProductParameterAdNetworkSourceIdentifier)) } } The project builds successfully, but before the #available(iOS 16.1, *) check is reached, the app crashes with: Symbol not found: _SKStoreProductParameterAdNetworkSourceIdentifier When I build the same project with Xcode 16.4 and launch it on an iOS 15 simulator, it runs without crashing. Investigation so far Because SKStoreProductParameterAdNetworkSourceIdentifier is ju
update Xcode 26 Beta 6 Fixed it Simulators may fail to boot during the first build after upgrading macOS; rebuilding after a short wait typically resolves the issue. (152328794)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
When I update the macOS from 15.5 to 15.6, Preview error. 1、I try remove simulator cache， sdk 2、remove Xcode build cache 3、reinstall Xcode 4、try with this method https://byby.dev/uninstall-xcode#:%7E:text=Delete%20old%20simulators%20and%20devices,moving%20them%20to%20the%20Trash but all failed swiftui log.txt
The behavior should be that only the fragments that fall in the view port + estimated overdraw region are re-drawn, and that should be true for all system versions. Thanks for creating the demo project for me. I've tried your project with my Xcode 26 Beta 6 + iOS 26 Beta 7 + iPhone 16 Plus, and don't see that the system re-draws all the paragraph. Here is what I do: a. Use the following print instead to better observe the fragments that are re-drawn: print(draw called in (rangeInElement)) b. Add more paragraphs to textContents so the content is longer. With that, here is what I see: Launch the app. Xcode shows the following log, indicating that only the first fragment is drawn. draw called in 0...1531 (Happens one time) Scroll a bit. Xcode shows the following log, indicating that only the first and second fragments are drawn: draw called in 0...1531 draw called in 1532...3237 ... (Repeats many times.) Scroll down to the bottom, clear the log, and then scroll a bit. Xcode sh
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
Right now, if I added a large swatch of contiguous code, the stage feature in Xcode is all or nothing — either I stage all the changes or I stage none of them. It would be a better UX if after spotting the isolates changes within that swatch that are final if I could select them and stage them. This way, it would be easy for me to easily green light all the changes I know are production ready, and then when I'm done, clearly see those which are not and easily be able to hone in on the changes that require some more thought.
Regarding the accessibility of Xcode, if there are specific things that you need to be productive where the currently available Xcode and macOS accessibly features don't go far enough, we'd like to hear details as an Enhancement Request in Feedback Assistant. — Ed Ford, DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
My app (called MuVis - Music Visualizer) passes the macOS App Store verification, but is failing the iOS verification. The errors indicate a problem with the Swift package github.com/Treata11/CBass. I have been in touch with the CBass package developer (Treata11) as well as the original BASS developers (un4seen.com). We think the problem is related to CBass swift-package config (which apparently works fine for mac, but doesn’t for iOS). The source code for the package is at the site package. All of us think that the package is configured correctly in accordance with the latest Apple package development documentation. Please tell us what is wrong with this package, and how to make it pass the iOS App Store verification. The Xcode error messages from validation testing include several items similar to: Upload Symbols Failed: inline-code The archive did not include a dSYM for the bass.framework with the UUIDs [18D5DBE2-3250-3EDE-B75C-D81B4E9F05AC, A88554A0-9087-3776-AC05-424B2D52F973, DEB682F5-ABBE-39D5
Just keep iOS on the latest beta, and Xcode also on its latest beta, which you currently have. The numbers don't always line up, that's normal. If there's something specific that is affecting your development that makes you want to do this, it would be helpful to hear what that is. — Ed Ford, DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
The configuration in your Xcode project, as shown in your feedback report, looks good to me, and so it is most likely that Xcode is unable to synchronize the configuration with Apple's developer portal to generate the right provisioning profile for you. Several things to check: Check if the configuration of the Xcode's Apple Accounts (Xcode > Settings > Apple Accounts) looks good. Follow the steps described in Setting Up Core Data with CloudKit to create a new project, and check if the issue is still there. This helps confirm that your developer account works. You can try with a brand new App ID and iCloud container, and then the App ID and iCloud container of your real app. Log in Apple's developer portal with the same account, and check if there is any warning or error message. Specifically, check if you have any agreement waiting for your action. Follow the steps described here to check if the your iCloud container is created and associated to your App ID. The asso
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I did some of investigation of this issue because I ran into the same problem when trying to convert an old project from groups to folders. I discovered what is happening is that Xcode 16 changes the model's current version to the last one alphabetically. I was able to reproduce it this way: Create a brand new, folder-based, Xcode project. Add an xcdatamodeld with one entity. Add a new model version and name it a. Make it current. Quit Xcode. Relaunch Xcode. Expected result: The a model version should still be current. Actual result: The original model version is current. I was able to reproduce with Xcode 16.2 and 16.4. It appears to be fixed in Xcode 26 beta 6. Based on these steps, one workaround appears to be to name the model versions alphabetically. Another workaround is to keep the xcdatamodeld file in a group, not a folder. And of course if you can switch to Xcode 26, then you don't need to workarounds above.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I have integrated Apple’s Foundation Model into my iOS application. As known, Foundation Model is only supported starting from iOS 26 on compatible devices. To maintain compatibility with older iOS versions, I wrapped the API calls with the condition if #available(iOS 26, *). The application works normally on an iPad running iOS 18 and on a Mac running macOS 26. However, when running the same build on a MacBook Air M1 (macOS 15) through iPad app compatibility, the app crashes immediately upon launch. The main issue is that I cannot debug directly on macOS 15, since the app can only be built on macOS 26 with Xcode beta. I then have to distribute it via TestFlight and download it on the MacBook Air M1 for testing. This makes identifying the detailed cause of the crash very difficult and time-consuming. Nevertheless, I have confirmed that the crash is caused by the Foundation Model APIs.
Topic:
Machine Learning & AI
SubTopic:
Foundation Models
Hello, Thank you for raising these concerns with AFM and OS versions. Re: However, when running the same build on a MacBook Air M1 (macOS 15) through iPad app compatibility, the app crashes immediately upon launch. Running a TF build from beta Xcode 26 on macOS 15.x through iPad app compatibility seems unreliable. A crash report can help diagnose the problem on the MBA which may be an isolated case for a specific configuration. Similarly, an Xcode project that shows the problem is ideal. All that said, let's: File a bug report for crash on launch (with details above) File a bug report requesting code-level guidance on how to use #available(iOS 26, *) with AFM See Feedback Assistant. DTS Engineer
Topic:
Machine Learning & AI
SubTopic:
Foundation Models
I am trying to localize the CFBundleDisplayName and OSBundleUsageDescription of a driver that is part of an app. I am able to use InfoPlist.strings files to localize the Bundle display name for the app, but when I try to use the same file as part of the driver, the name displayed in settings for the app does not change correctly. In fact, it seems to follow the default language set in the xcode project. If the default language is not included in the suite of InfoPlist.strings files, it seems to take the string from the info.plist file. sometimes it just seems to take the English version regardless of the default language or tablet language. Has anyone had success with this?