Search results for

Xcode

92,303 results found

Post

Replies

Boosts

Views

Activity

Reply to URLRequest(url:cachePolicy:timeoutInterval:) started to crash in iOS 26
[quote='868298022, bims, /thread/806594?answerId=868298022#868298022, /profile/bims'] Looking at the ips-file I found that it does not show the finding that Xcode show [/quote] Right. Xcode has MTE smarts beyond what the human readable crash report shows. To see the underlying data, open the JSON crash report and search for memoryErrorReport. With some reformatting you get this: memoryErrorReport : { faultAddress:0x0c00000d9de112c0, blamedAllocation: { size:48, allocationTrace:…, deallocationTrace:…, isFreed:true, address:0x0c00000d9de112c0 }, errorType:use-after-free }, The allocationTrace and deallocationTrace backtraces need further massaging. I did a hack-ish job of that and have included the results at the end of this post. I wanted the JSON crash report so that I could run it through some internal tools. I was able to do the first part of that today. I was hoping it might point me at some known bugs. It did, but those were resolved a while bug and thus are unlikely to be the cause of t
2w
Reply to Xcode and Reading documents from a URL connection.
[quote='868358022, Apple_Fox, /thread/807599?answerId=868358022#868358022, /profile/Apple_Fox'] Is that something that would cause errors for downloading the documents … ? [/quote] It very much depends on the server. Given a URL for something downloadable, some servers allow you to download the resource directly and other require you to jump through hoops. You can see this even on Apple servers. For example, SF Symbols 7 is directly downloadable: https://devimages-cdn.apple.com/design/resources/download/SF-Symbols-7.dmg but Xcode 26.1.1 is not: https://download.developer.apple.com/Developer_Tools/Xcode_26.1.1/Xcode_26.1.1_Universal.xip In the Xcode case, the server redirect the download request to a login page. That login page assumes that the client is a person using a web browser, and it’s very hard to programmatically deal with the required authentication. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Announcing the Swift Student Challenge 2026
Announcing the Swift Student Challenge 2026 Every year, Apple’s Swift Student Challenge celebrates the creativity and ingenuity of student developers from around the world, inviting them to use Swift and Xcode to solve real-world problems in their own communities and beyond. Learn more → https://developer.apple.com/swift-student-challenge/ Submissions for the 2026 challenge will open February 6 for three weeks, and students can prepare with new Develop in Swift tutorials and Meet with Apple code-along sessions. The Apple Developer team is here is to help you along the way - from idea to app, post your questions at any stage of your development here in this forum board or be sure to add the Swift Student Challenge tag to your technology-specific forum question. Your designs. Your apps. Your moment.
6
0
1.1k
2w
Reply to Cannot submit apps with Xcode 26.2 RC
I installed the RC (replacing 26.1), tested my app, and went to create a release for an update that happens to need to be released pretty quickly. I recall from previous experience RC builds could submit apps to the App Store so figured I wouldn’t run into any problems. Now I’m blocked. I could go download Xcode 26.1 and redownload the iOS 26.1 Simulator and retest my app with that SDK version but that’s a lot of wasted time/resources only to release the update on a very soon to be out of date SDK. :/ Do you expect this RC build to be accepted in the near future?
2w
NavigationSplitView + inspector causes Sidebar state issues on Mac Catalyst
Hi everyone! I've encountered an issue on Mac Catalyst: using the latest inspector modifier causes abnormal Sidebar and Columns state in NavigationSplitView. Sample Code: struct ContentView: View { @State private var isPresented = false var body: some View { NavigationSplitView { List { ForEach(0..<20, id: .self) { item in Text(Item (item)) } } } content: { List { ForEach(0..<20, id: .self) { item in Text(Item (item)) } } } detail: { List { } } .inspector(isPresented: $isPresented) { Form { } } } } Steps to reproduce: Xcode 16 beta 7, create a new iOS project Paste the code above Enable Mac Catalyst Run on Mac (macOS 15 beta 9) Press Command+N three times to open 3 new windows Click the Sidebar Toggle button The issue occurs (see screenshot below) Through testing, I found that as long as the inspector modifier is attached, the issue occurs. Also, the problem only appears in the 3rd and subsequent newly opened windows—the first two windows work as expected. FB20061521
1
0
260
2w
Reply to Cannot submit apps with Xcode 26.2 RC
Thank you for providing this information. You are correct that the 26.2 RC is still not permitted to submit builds. The team typically updates this page when it is ready and open to submissions. https://developer.apple.com/help/app-store-connect/release-notes/ On the release notes, you’ll see something like “You can now upload apps built with Xcode….” I understand that submitting with RC versions is often possible, and I acknowledge that this may be an inconvenience. Please continue to monitor the release notes for updates. Could you please provide any reasons why you are unable to submit with the previous released version? Albert Pascual
  Worldwide Developer Relations.
2w
Reply to Permission error occurs when I use setDefaultApplication(at:toOpen:completion:)
Sounds like either it's not working right or the documentation needs to be updated to explain how to get it working. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: App & System Services SubTopic: General Tags:
2w
Reply to Xcode not updating recent projects
Thank you for sharing your experience. It appears that you are encountering an unusual issue with Xcode not displaying recent projects. To resolve this, please ensure that both macOS and Xcode are updated to the latest versions compatible with your system. While you have mentioned your current versions, it is advisable to double-check for any minor updates. Could you kindly provide a screenshot of Xcode when you attempt to open the “Recents” folder using the “File” menu? Please note that the screenshot should display the contents of the “Recents” folder. File -> Open Recent Please indicate whether you observe any recent projects or if the list is completely empty. Albert Pascual
  Worldwide Developer Relations.
2w
Xcode not updating recent projects
My Xcode does not show my Recent projects for a while now. I have different projects on my Mac that I open using Xcode and it can't remember the recent ones and never shows it. Does anyone know how to fix that? I've tried to clean caches, restart the Mac, download the Xcode again... MacOs: Tahoe 26.1 Xcode: 26.1.1
1
0
38
2w
macOS 15 (Sequoia): Endpoint Security client runs by hand, but LaunchDaemon fails with TCC “Full Disk Access” denial on unmanaged Macs
Platforms: macOS 15.x (Sequoia), Intel-Based App type: Endpoint Security (ES) client, notarized Developer ID app + LaunchDaemon Goal: Boot-time ES client that runs on any Mac (managed or unmanaged) Summary Our ES client launches and functions when started manually (terminal), but when loaded as a LaunchDaemon it fails to initialize the ES connection with: (libEndpointSecurity.dylib) Failed to open service: 0xe00002d8: Caller lacks TCC authorization for Full Disk Access We can’t find a supported way to grant Full Disk Access (SystemPolicyAllFiles) to a system daemon on unmanaged Macs (no MDM). Local installation of a PPPC (TCC) profile is rejected as “must originate from a user-approved MDM server.” We’re seeking confirmation: Is MDM now the only supported path for a boot-time ES daemon that requires FDA? If so, what’s Apple’s recommended approach for unmanaged Macs? Environment & Artifacts Binary (path placeholder): /Library/Application Support///App/.app/Contents/MacOS/ Universal (x86_64 + arm64
10
0
1.3k
2w
Reply to Popovers are broken on macCatalyst
@stoope Thanks for your post and code. Using your code I was able to show the popover without seen a crash using Xcode Version 26.2 beta (17C5013i) that is in beta at the developer website. Can you try that and let me know if resolves your issue? I would recommend to provide a focused sample and a link to the repository so we can test and see the issue. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2w
Reply to moving project to new account
Thank you for your post. Migrating your Swift project from a free Apple Developer account to a paid one does not necessitate rebuilding the project from scratch. Here is a step-by-step guide to facilitate a seamless transition: Log into Your Paid Account: Sign in to your Mac using the Apple Account associated with your paid Developer account. Open Xcode and navigate to Xcode > Preferences > Accounts. Click the “+” button to add your paid Apple ID if it is not already listed. Update Code Signing: Open your Xcode project. Select your project in the Project Navigator to access the project settings. Navigate to the “Signing & Capabilities” tab for your target. Ensure that your team is configured to your paid account. If not, click on the team dropdown and select your paid developer account. Adjust Provisioning Profiles: Xcode typically automates the downloading of provisioning profiles when signed in with the paid account. You can force a refresh by visiting Window &g
2w
Reply to UITabBar ignores font in iOS 26.2
Thanks for your post. Do you have a focused sample project where we can see the fonts in the bundle but the iOS 26.2 is ignoring but working on previous versions? To ensure your custom font is applied to UITabBar items on iOS 26.2, consider the following steps: Double-Check Font Availability: Ensure that the custom font AvenirNext-DemiBold is included in your app's bundle. Check your Info.plist to confirm that the font is properly listed under the UIAppFonts key. Use configureWithOpaqueBackground: Try setting the appearance configuration using configureWithOpaqueBackground, which might provide better consistency across different iOS versions. Debug Using Runtime: Use Xcode's debugger to inspect the titleTextAttributes at runtime on iOS 26.2 to verify if your attributes are being overwritten or ignored. I would be delighted to assist you if you could provide a focus sample that I can analyze against iOS 26.2. If you're not familiar with preparing a test project, take a look at Creating a test project.
Topic: UI Frameworks SubTopic: UIKit Tags:
2w