let package = Package( name: "MyLibrary", platforms: [.iOS(.v17)], There is no ios26 option. How do I build it under ios26? thanks

Where are the local documentation files location on MacOS? None of the existing data on the internet is applicable anymore. Trying to bundle documentation for use in an LLM and the developer site is unusable for crawling. Thanks! *.docset

Hi I developed an iPhone app but now I want to release the same app for iPad and Mac (Design for iPad). I made the changes below but I still not been able to install the app on my Mac. It says the app is incompatible but my Mac is MacBook Pro M2 which fills the requirements to install it. Things I did so my iPhone app could have support for iPad and Mac Added iPad and Mac (Designed for iPad) for the supported destinations Change the Status Bar Style to Require full screen Changed iOS minimum Deployments iOS to 17.6 Updated the launch screen logo so stays in the middle Xcode version 16.2 See the sccreenshots of the Xcode configuration and of the TestFlight on my MacBook Pro M2 Is there anything else I need to do? Thanks.

I have the this issue when I run the app on iOS Simulator after updating to app to make it compatible with Xcode-16 and iOS-18. after upgradation to Xcode-16 its giving the above error "Executable path is a directory" .This app work fine on Xcode-15 . Note - The issue with iOS Simulator only. From XCode-16 build is created successfully and installed in iOS device.

Hey all wondering if anyone has seen this new in xcode 26 beta 2 it seems any NIBS with a UISwitch will 'error' saying please submit a feed back and attach the log, i did submite a feedback but looking at the log it simply says : the tool closed the connection (IBAgent-iOS) then if you just build again it builds fine and runs fine, but if you switch from simulator to device and build the error will happen again, but same thing build again and it works. I opened my NIBS with the switch and they open just fine, no errors or anything so im wondering if its something in the build system. For any xcode engineers here: here is my feedback number 18348463

I am using a Mac computer running macOS 15.5 with Xcode version 16.3 (16E140) and an iPhone XS Max on iOS 18.5. When debugging my app on the real device using Xcode, the app gets stuck on the launch screen and fails to proceed to the main interface. There is no output in the Xcode console, and the top of the window continuously shows "attaching to [app name] on [iPhone name]". Here are the details: The same issue occurred when the phone was running iOS 18.4.1. When I tested on another real device running iOS 17, the app launched and ran normally. I’ve tried clearing the cache, but it didn’t help. I deleted the ~/Library/Developer/Xcode/iOS DeviceSupport folder, let it re-download the necessary files, and ran the app again, but the issue persists. I’m currently out of ideas and would appreciate any assistance.

I am attempting to generate screenshots at various logical times using a watchOS 11 simulator. % xcrun simctl status_bar "Apple Watch Series 10 (46mm)" override --time 9:06 An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=45): Simulator device failed to complete the requested operation. Operation not supported Underlying error (domain=NSPOSIXErrorDomain, code=45): Status bar overrides not supported on this platform. Operation not supported Using WatchOS Clock Settings gives me at most 59 minutes in which to succeed. Even if I had a physical watch for every series and size, I would have to wait up to 23 hours before being able to generate my marketing screenshots to support various user scenarios. With three settings variations, a minimal wait time to get to good marketable content would be on the order of 1 month per app version.

I am passing UUID Key from View1 to View2. In View2, I need to Fetch entries using TabKey. userId is global variable working fine. Giving error TabKey. Please help. how to get rid of this error. If I keep this logic inside init method, Getting new error saying that "Cannot convert value of type 'FetchedResults' to expected argument type 'Binding' Here is the Code. @FetchRequest( sortDescriptors: [NSSortDescriptor(keyPath: \Table2.date, ascending: false)], predicate: { guard let currentUserId = AppSession.shared.currentUserId else { return NSPredicate(value: false) // Or handle the nil case as needed } return NSPredicate(format: "userId == %@ AND itemKey == %@", currentUserId as CVarArg, TabKey as CVarArg ) }(), animation: .default ) private var itab: FetchedResults

If I do this: NSString *name = @"Jim"; NSMenuItem *menuItem = [[NSMenuItem alloc]init]; // Analyze does show localization warning when format string is used. menuItem.title = [NSString stringWithFormat:@"Hello %@",name]; I expect to get the following warning: User-facing text should use localized string macro But I don't. However if I do this: menuItem.title = @"What"; I do get the warning about localization as expected and as desired when I run Analyze. Is this considered a bug? Thanks!

I am a bit confused. My understanding previously was that a modulemap was required in order to have a bridging header be generated. Now it has come to my attention that a modulemap is both a build input and something you can put in the Modules folder of the built product if you so choose. I have tried reading the clang modulemap documentation, but am really struggling to connect most of what it says to the problem at hand. In a project I am working on, the generation of the modulemap file is quite problematic. The framework imports C++ libraries and itself writes Objective-C++ wrappers for them. Currently, the modulemap file is both set as the Module Map File in "Build Settings" and presumably used when the Swift project later imports it. In this project the modulemap is a list of the objective-c++ header files then export * I am trying to understand what I would lose if I do one or both of two things: What happens if I dont set this module map file in the build settings for the objective-c++ framework? What happens if I dont have a modulemap involved whatsoever in this objective-c++ framework and then it is imported into Swift? And does any of this change if its compiled as a static vs dynamic library? What if I embed it vs not embed it? Because the build in the real project is so complicated its hard to isolate what is going on. So I built a smaller sample app. There is CFramework which has an objective-c++ class. There is SwiftProject which imports that framework and is purely Swift. It imports the module and uses it. I did not write a modulemap file, and the Swift project builds just fine. In the timeline it: Prepares packages Computes target dependency graph Builds static cache for iPhoneSimulator18.2sdk As near as I can tell even though the objective-c++ framework is not built with a modulemap in its build settings and there is not a modulemap included in the framework everything works. So then the modulemap file is useless? Perhaps it speeds things up but what step would theoretically be skippable?

Hi everyone, We're developing an AR app using Unity with Vuforia for object detection. Our app works well in full-screen mode, including detection and post-detection phases. However, we're facing a specific issue in iPad Split View multitasking mode. Problem: The AR camera (Vuforia-based) freezes during object detection if another app is opened in Split View. Post-detection, everything works fine in Split View. The problem only occurs during detection. Testing Environment: iPadOS 16+ Unity with Vuforia plugin Using EnableMultitaskingCameraAccess() method with AVFoundation to support camera multitasking AR scene is set up properly with detection capabilities in full-screen

Apple's push cannot receive information, use the open-source library JdSoft. Apple.Apns.Notifications Because I am not familiar with it, I modified Tls12. Does anyone know how to modify this open-source library to achieve push functionality apnsStream.AuthenticateAsClient(this.Host, this.certificates, System.Security.Authentication.SslProtocols.Tls12, false)

Using Xcode 26.0 beta (17A5241e) Wanted to try out raw identifiers for Swift Testing tests, and while they work, syntax colorization is dreadful. Much less readable then just using a custom name with @Test. Feedback: FB18260756 Example with a raw identifier of some example test name:

Hi guys, recently I've been investigating new UI Testing in Xcode7. There seems to be limited APIs we can call direct in UI test. Can I include header files and call public API of my tested app in UI Test? so that I can have more flexibility to set my app status before running test. I intent to call API method "-(void)reloadURL:(NSURL *)url" of my app in UI Test, but test failed with "XCTRunner -[_XCTRunnerAppDelegate myAppDelegateUtils]: unrecoginzed selector sent to instance 0x7cf0a992fe10"In Unit Test we can call any API of the tested app, does it support in UI Testing too? I'm a start learner of Xcode and its testing...could anyone help to answer this question? Thanks!

Is there some official documentation about the SYSTEM_VERSION_COMPAT environment variable and how it affects the version reported by tools like sw_vers and whether the presence of that environment variable affects APIs like NSOperatingSystemVersion? I ask this in context of recent macOS 26 Beta version where NSOperatingSystemVersion from older versions of XCode (for example XCode 15.4) report the macOS version as 16.0.

At the last place I worked it took roughly 5 minutes to do an application build. Which in turn made doing any sort of TDD or ever just regular Unit Tests extremely painful to do as the cycle time was simply too long. But that got me thinking. In recent versions of Xcode, Apple added Previews for SwiftUI Views that basically showed code changes to the View in real time. And Previews were made possible by extremely targeted compilation of the view in question. So... what if instead of a Preview pane in the Xcode IDE there was a Test pane the could be displayed such that Tests for a piece of code could be created and run almost immediately? Perhaps by adding a #Testing section to your code #Testing(MyService.self) // Define the entity to be tested. If you could drop the turnaround time AND provide a test playground for service level code that could speed development of such code greatly... and encourage interactive test development at the same time. What do you think?

Hi , I am currently encountering issues while running a Titanium application using Xcode 16. I would like to request your guidance on resolving the following problems: When running the Titanium app on a real device, I receive the following warning in Xcode and the app does not proceed beyond this point and the app is crashing on launch. warning: (arm64) /Users/Library/Developer/Xcode/DerivedData/Procedures-hamsarmfbtnowbcdocpmydtuafnp/Build/Products/Debug-iphoneos/Procedures.app/Procedures empty dSYM file detected, dSYM was created with an executable with no debug info. Thank you

I'm integrating Apple Pay with PayFort in a Swift iOS application, and I’m currently working on preparing a valid purchase request using Apple Pay, as described in PayFort’s documentation: 🔗 https://docsbeta.payfort.com/docs/api/build/index.html?shell#apple-pay-authorization-purchase-request The documentation outlines the following required parameters: apple_data apple_signature apple_header apple_transactionId apple_ephemeralPublicKey apple_publicKeyHash apple_paymentMethod apple_displayName apple_network apple_type Optional: apple_applicationData I understand these should be derived from the PKPayment object after Apple Pay authorization, but I’m having trouble mapping everything correctly. Here’s what I’m seeing in code: payment.token // Returns something like: <PKPaymentToken: 0x28080ae80; transactionIdentifier: "..."; paymentData: 3780 bytes> payment.token.paymentData // Contains 3780 bytes of encrypted data payment.token.paymentData.base64EncodedString() // Returns a long base64 string, which at first glance seems like it could be used for apple_data, // but PayFort doesn't accept it as-is — so this value appears to be incomplete or incorrectly formatted I can successfully retrieve the following values from payment.token.paymentMethod: apple_displayName apple_network apple_type However, I’m still unsure how to extract or build the following in the format accepted by PayFort: apple_data apple_signature apple_header apple_transactionId apple_ephemeralPublicKey apple_publicKeyHash apple_paymentMethod These may be contained within the paymentData JSON, but I’m not sure how to decode it or if Apple allows decrypting it in a way that matches PayFort’s expected format. How can I correctly extract or build apple_data, apple_signature, and apple_header from the Apple Pay token? Also, how should I handle the decryption or decoding (if necessary) of paymentData to retrieve values like apple_transactionId, apple_ephemeralPublicKey, and apple_publicKeyHash? If anyone has successfully set this up or has example code that bridges Apple Pay and PayFort’s expected request format, it would be super helpful! Thanks in advance 🙏

Hi, I don't understand why Xcode fails to build my app when following logic was uncommented as part of ternary operator (as highlighted in attachment). Can somebody help me please ?? Thx. ... : shelterViewModel.getShelter(row: row, column: column).productId == ... ? Color.yellow ...

Xcode 16.2. When calling openURL:options:completionHandler: when in the simulator for a link in the app store (for example: http://itunes.apple.com/us/app/slidewords/id503737864?mt=8) behavior is fine for simulated iPads, not for simulated iPhones. When the simulated device is an iPad, the call correctly opens the app store link. When the simulated device is an iPhone, an error message "Safari cannot open the page because the address is invalid." Note: the call works on an an actual iPhone (iPhone SE 3rd generation, unsure about other devices).