Active questions tagged xcode - Stack Overflow

Preventing Xcode from auto-versioning files

noemail@noemail.org (Pheepster) — Fri, 27 Feb 2015 17:22:12 GMT

This is a general Xcode question but here goes.

When a nib is opened, Xcode auto-versions it, causing it to appear as a changed file in Git/SourceTree. This occurs regardless of whether any real changes have occurred in the nib. The behavior occurs in other file types as well, like image asset catalogs.

When working in a large app with many nibs or large asset catalogs, opening/closing without changes can result in a large list of changed files and increase the chances of unintentionally staging and committing, etc.

Does anyone know of a way to prevent Xcode from auto-versioning?

How to use UILocalNotification to open specific view containing CoreData

noemail@noemail.org (The Dude) — Mon, 3 Aug 2015 19:06:16 GMT

I am developing an application where the user can set a notification reminder to change the password of the CoreData instance to which the reminder was set.

When the user hits the "First Action" button I want them to be redirected to the second and fourth view.

Here's what I'm trying

Relevant code from my AirlineViewController.swift and AppDelegate.swift

AirlineViewController.swift:

@IBAction func buttonTapped(sender: AnyObject) {
    NSNotificationCenter.defaultCenter().addObserver(self, selector:"showAMessage:", name: "actionOnePressed", object: nil)
    NSNotificationCenter.defaultCenter().addObserver(self, selector:"drawAShape:", name: "actionTwoPressed", object: nil)

    
    var dateComp:NSDateComponents = NSDateComponents()
    dateComp.year = 2015;
    dateComp.month = 08;
    dateComp.day = 03;
    dateComp.hour = 21;
    dateComp.minute = 03;
    dateComp.timeZone = NSTimeZone.systemTimeZone()
    
    var calender:NSCalendar = NSCalendar(calendarIdentifier: NSCalendarIdentifierGregorian)!
    var date:NSDate = calender.dateFromComponents(dateComp)!
    
    
    var notification:UILocalNotification = UILocalNotification()
    notification.category = "FIRST_CATEGORY"
    notification.alertBody = "Hi, I am a notification"
    notification.fireDate = date
    
    UIApplication.sharedApplication().scheduleLocalNotification(notification)
    
}


func drawAShape(notification:NSNotification){
    println("drawAShape")
    var view:UIView = UIView(frame:CGRectMake(10, 10, 100, 100))
    view.backgroundColor = UIColor.redColor()
    
    self.view.addSubview(view)
    println("drawAShape")
    
}

func showAMessage(notification:NSNotification){
    
    var message:UIAlertController = UIAlertController(title: "A Notification Message", message: "Hello there", preferredStyle: UIAlertControllerStyle.Alert)
    message.addAction(UIAlertAction(title: "OK", style: UIAlertActionStyle.Default, handler: nil))
    
    self.presentViewController(message, animated: true, completion: nil)
}

AppDelegate.swift

func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {

    //Actions
    var firstAction:UIMutableUserNotificationAction = UIMutableUserNotificationAction()
    firstAction.identifier = "FIRST_ACTION"
    firstAction.title = "First Actions"
    
    firstAction.activationMode = UIUserNotificationActivationMode.Foreground
    firstAction.destructive = true
    firstAction.authenticationRequired = false
    
    var secondAction:UIMutableUserNotificationAction = UIMutableUserNotificationAction()
    secondAction.identifier = "SECOND_ACTION"
    secondAction.title = "Second Actions"
    
    secondAction.activationMode = UIUserNotificationActivationMode.Foreground
    secondAction.destructive = false
    secondAction.authenticationRequired = false
    
    var thirdAction:UIMutableUserNotificationAction = UIMutableUserNotificationAction()
    thirdAction.identifier = "THIRD_ACTION"
    thirdAction.title = "Third Actions"
    
    thirdAction.activationMode = UIUserNotificationActivationMode.Background
    thirdAction.destructive = false
    thirdAction.authenticationRequired = false
    
    //Category
    
    var firstCategory:UIMutableUserNotificationCategory = UIMutableUserNotificationCategory()
    firstCategory.identifier = "FIRST_CATEGORY"
    
    let defaultActions:NSArray = [firstAction, secondAction, thirdAction]
    let minimalActions:NSArray = [firstAction, secondAction]
    
    firstCategory.setActions(defaultActions as [AnyObject], forContext: UIUserNotificationActionContext.Default)
    firstCategory.setActions(minimalActions as [AnyObject], forContext: UIUserNotificationActionContext.Minimal)
    
    //NSSet of all our categories
    let categories:NSSet = NSSet(objects: firstCategory)
    
    
    let types:UIUserNotificationType = UIUserNotificationType.Alert | UIUserNotificationType.Badge
    
    let mySettings:UIUserNotificationSettings = UIUserNotificationSettings(forTypes: types, categories: categories as Set<NSObject>)
    
    UIApplication.sharedApplication().registerUserNotificationSettings(mySettings)
    
    
    return true
}

func application(application: UIApplication!,
    handleActionWithIdentifier identifier:String!,
    forLocalNotification notification:UILocalNotification!,
    completionHandler: (() -> Void)!){
        
        if (identifier == "FIRST_ACTION"){
            
            NSNotificationCenter.defaultCenter().postNotificationName("actionOnePressed", object: nil)
            
        }else if (identifier == "SECOND_ACTION"){
            NSNotificationCenter.defaultCenter().postNotificationName("actionTwoPressed", object: nil)
            
        }
        
        completionHandler()       
}

The problem with this code is that it just opens the last view or the first if the app is completely closed.

Can anybody help me

Unable to install app on Xcode 15 - Failed to verify code signature

noemail@noemail.org (Jorn Rigter) — Wed, 15 Nov 2023 15:32:42 GMT

The installation of my app was working fine before, and literally nothing changed when I tried to run it on my device, but I'm getting the following error when trying to install (iOS 17.1.1, Xcode 15.0.1):

"Unable to install {app name}"

Failed to verify code signature of {path name} (a valid provisioning profile for this executable was not found).

Verify that the Developer App certificate for your account is trusted on your device. Open Settings on the device and navigate to General -> VPN & Device Management, then select your Developer App certificate to trust it.

Problem is, I can't grant that permission under General -> VPN & Device Management, nothing of the sorts shows up there.

I was searching for 30 minutes before finding a solution, so posting here in case it is useful to some folks!

Get application logs from tvOS [closed]

noemail@noemail.org (Sahil) — Sun, 26 Apr 2026 12:20:58 GMT

I am building an automated workflow to run on real tvOS devices.

I am able to install and launch the application on the Apple TV but I can't find any way to get the logs that are generated by the application.

I use the command

xcrun devicectl device process launch --device <UDID> <BUNDLE_ID>

and this launches the app on the TV but I can't get the logs.

It would run in headless environment so I can't look up Xcode GUI to logs it has to be in some log file that I can later parse as per my use case.

Mysterious error message: "Unable to obtain a task name port right for pid {_windowserver}: (os/kern) failure (0x5)" when calling newDocument() [closed]

noemail@noemail.org (lpetrich) — Sun, 26 Apr 2026 10:54:12 GMT

I have recently restarted macOS Cocoa development, and I am running a M4 iMac with Tahoe 26.4.1, and using Xcode version 26.4.1 (17E202).

When my app starts, I get no error messages, but what triggers an error message is selecting File > New...

This successfully calls AppDelegate.newDocument() but before executing any of that function's code, the app emits this error message:

Unable to obtain a task name port right for pid {_windowserver}: (os/kern) failure (0x5)

I have replaced the pid number with what that process runs: _windowserver .

Is there some permission that I need that I am not setting correctly?

Wrong language shown in AppStore

noemail@noemail.org (Menslo) — Sun, 7 Jan 2024 07:20:10 GMT

I probably have more of a beginner's question, but I just can't get any further. I have programmed my first app and it is now in the Apple App Store. Yay. The app is in German, but the App Store lists English as the app language. In App Store Connect, I have entered German as the primary language and the app language. I did a bit of research and it seems to be due to the settings in Xcode. In the app info in Xcode, the default localization development language is specified. Is it related to this? How can I change the development language in Xcode so that the app language in the App Store is shown as German? I have read that it is not recommended to set the language manually to German. I would therefore like to set the development language to German. Or does it make more sense to simply select the localization manually in the info? I tried to set primary language and app language in App Store Connect - but the App language in App Store is still shown as English.

Xcode 16.0: "Unexpected service error: The Xcode build system has crashed" while building iOS project [closed]

noemail@noemail.org (Waseem Kurne) — Tue, 17 Sep 2024 16:33:24 GMT

I am encountering a build failure in Xcode 16.0 where the build system crashes with an unexpected service error.

Environment

Xcode: 16.0
react native version: 0.73.8
macOS: 15

Error

During the build process, Xcode fails with the following message:

unexpected service error: The Xcode build system has crashed. Build again to continue.

Expected Behaviour

The project should build successfully without crashing the Xcode build system.

Steps to Reproduce

Open the project in Xcode 16.0
Select a simulator or physical device
Click Build or Run The build system crashes with the above error

What I Tried

Cleaned the build folder (Shift + Cmd + K)
Deleted DerivedData
Restarted Xcode and system
Reinstalled dependencies (if React Native: node_modules + pod install)
Checked for invalid project configurations

What are the possible causes of this Xcode 16.0 build system crash, and how can it be resolved?

pod install Xcode Error Failed to save foo.xcodeproj

noemail@noemail.org (make) — Tue, 18 Jun 2024 08:39:16 GMT

I've been encountering an issue where, after running pod install, Xcode consistently throws an error: "Failed to save foo.xcodeproj." To clear this warning, I have to click through it more than 50 times.

This has become quite frustrating, as it happens every time I run pod install. Is there a way to prevent this error from occurring?

Trying to build just after installing cordova and getting error after error

noemail@noemail.org (David Markowitz) — Thu, 23 Apr 2026 04:58:29 GMT

I've gone through the documentation, following the steps for installation and app creation, but every time I try to build, I get at least one error, sometimes more. I've noticed at least one step eft out of the docs - adding a developer team in Signing and Capabilities in Xcode. I've also noticed that building for ios from the terminal fails because the default configuration it tries to use is { platform:iOS Simulator, OS:latest, name:iPhone SE (3rd generation) }, and it results in the error Unable to find a device matching the provided destination specifier. However, I can fix that by specifying the destination with the --buildFlag (or building in Xcode).

The one error that keeps happening when building in terminal is this one (which I get when building with --verbose):

Command failed with exit code 65: xcodebuild -workspace App.xcworkspace -scheme App -configuration Debug -sdk iphonesimulator -destination platform=iOS Simulator,name=iPhone 17 build
Error: Command failed with exit code 65: xcodebuild -workspace App.xcworkspace -scheme App -configuration Debug -sdk iphonesimulator -destination platform=iOS Simulator,name=iPhone 17 build
    at makeError (/Users/[my project path]/node_modules/cordova-ios/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/Users/[my project path]/node_modules/cordova-ios/node_modules/execa/index.js:118:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Promise.all (index 0)

(I removed my path from the code above) What is causing this??

And the latest errors I'm getting when trying to build in Xcode are these:

/Users/[path to my project]/platforms/ios/App/Assets.xcassets: Failed to read file attributes for "/Users/[path to my project]/starvoyage/platforms/ios/App/Assets.xcassets"

/Users/[path to my project]/platforms/ios/App/Assets.xcassets: None of the input catalogs contained a matching stickers icon set, app icon set, or icon stack named  "AppIcon".

No idea what these are either. FWIW, I'm not experienced with Xcode (or Cordova for that matter), so really not sure what I'm doing. It really seems like the Cordova docs for starting out are not complete or updated.

Trying to use /usr/bin/gcc instead of Xcode clang for purposes of C++20

noemail@noemail.org (Jeff Swearingen) — Thu, 23 Apr 2026 16:22:25 GMT

I'm attempting to use the gcc compiler installed at /usr/bin/gcc by homebrew on my MacBook running Tahoe. Every time I run it, it defaults to Xcode's clang instead. I am attempting to compile C++20 programs and have the flags set to -std=c++20, but am still getting errors with commands such as import std;

I'm running gcc -std=c++20 main.cpp

My path is:

/usr/bin/gcc /opt/homebrew/opt/node@22/bin /opt/homebrew/opt/ruby/bin /opt/homebrew/bin /opt/anaconda3/condabin /opt/homebrew/opt/node@22/bin /opt/homebrew/opt/ruby/bin /opt/homebrew/bin /Library/Frameworks/Python.framework/Versions/3.14/bin /Library/Frameworks/Python.framework/Versions/3.14/bin /Library/Frameworks/Python.framework/Versions/3.14/bin /Library/Frameworks/Python.framework/Versions/3.13/bin /usr/local/bin /System/Cryptexes/App/usr/bin /usr/bin /bin /usr/sbin /sbin /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin /opt/pkg/env/active/bin /opt/pmk/env/global/bin /Library/Apple/usr/bin /usr/local/go/bin

When I run gcc -v, this is what I get:

Apple clang version 21.0.0 (clang-2100.0.123.102)

Target: arm64-apple-darwin25.4.0

Thread model: posix

InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Build input file cannot be found {PATH} did you forget to declare this file as an output

noemail@noemail.org (iiiivaska) — Wed, 5 Oct 2022 16:34:36 GMT

After creating and deleting the Objective-C file with the header, an error appeared. How can I fix it?

error build: Build input file cannot be found:
'/Users/iiiivaska/Desktop/To-Do List/To-Do List/View/Cells/To-Do List-Bridging-Header.h'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it?

How to add a quick and dirty, default/dummy icon to Xcode AppIcon asset class?

noemail@noemail.org (Doug Null) — Tue, 10 May 2022 00:41:41 GMT

My app doesn't upload to App Store Connect, for TestFlight, because app store icon is missing (see below error).

What's the fastest way to populate the AppIcon asset class, to solve this?

I don't care what the icon is; this is only an internal test app.

ITMS-90713: Missing Info.plist value - A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'com.company.KPdiag9May2022b'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key.

Xcode 26.4 build error: "call to consteval function 'fmt::basic_format_string' is not a constant expression" in React Native iOS build

noemail@noemail.org (Waseem Kurne) — Tue, 7 Apr 2026 09:09:10 GMT

I am encountering a build error while compiling a React Native iOS project using Xcode 26.4.

Environment

React Native: 0.81.x
Xcode: 26.4
macOS: 26.4

Error During the build process, I get the following error:

call to consteval function 'fmt::basic_format_string' is not a constant expression

Expected Behaviour The project should compile and run successfully on iOS without build errors.

Actual Behaviour The build fails during compilation with the above error.

Steps to Reproduce

Create or open a React Native project
Install dependencies (npm install / yarn)
Open the iOS project in Xcode 26.4
Attempt to build the project
The error appears during compilation

What I Tried

Cleaned the build folder
Deleted DerivedData
Reinstalled node_modules
Ran pod install again
Tried rebuilding multiple times

What is the root cause of this error in Xcode 26.4, and how can it be resolved in a React Native iOS project?

How can I access 'package' members declared in a Swift package from an Xcode project?

noemail@noemail.org (Sweeper) — Tue, 21 Apr 2026 03:39:38 GMT

I am building a framework for others to use. The framework itself is not built with SPM, but with Xcode. (It has a .xcodeproj file.)

Now I want to use macros in this framework. As far as I know, both the macro implementation and macro declaration must be in a Swift Package. So I created a new Swift Package with --type macro, and added that as a local package dependency of the framework.

Since the macro declaration is public, the users using my framework will also be able to use the macro by importing the modules of the Swift Package. This is undesirable.

I found that the package access modifier seems to be designed to solve this problem. It is supposed to allow different modules that form one single "package" to access each others' code. It doesn't seem like this is only applicable to SPM projects, as it mentions

Swift as a language leaves it up to the build system to define the boundaries of a package.

So I assume there is some build setting in Xcode that allows me to include the SPM packages to be considered the same "package" as the Xcode framework target.

I found a build setting named SWIFT_PACKAGE_NAME, which sounds promising:

An identifier that allows grouping of modules with access to symbols with a package access modifier.

But I don't know what to set this to. I tried setting it to the same name as the Swift package containing the macro (the name passed as the first parameter to Package.init in Package.swift), but I still cannot access package symbols.

What can I do to prevent users of my framework from accessing the Swift Packages that my framework depends on?

Kotlin Multiplatform Mobile unable to run on iOS: Execution failed for task ':shared:compileKotlinIosX64'

noemail@noemail.org (Fatin Wasta) — Tue, 9 Feb 2021 05:24:18 GMT

I have created fresh project(Hello World) in KMM followed by their official website. In android it works smooth but when I am trying to run in XCode it's giving errors because of which I am unable to build / run the xcode project. I have attached screenshots and logs for my errors. Somehow xcode scheme is not getting generated in the KMM platform that's what I am guessing. Can anyone please help me understand what am I missing? Any help would be appriciated.

Following is my dev env:

Xcode 11.4.1
Android 4.1.2
Kotling Plugin version 1.4.30 (stable)
KMM 0.2.0```


XCode Logs:

> Task :shared:compileKotlinIosX64
Downloading native dependencies (LLVM, sysroot etc). This is a one-time action performed only on the first run of the compiler.
Extracting dependency: /Users/fatin/.konan/cache/clang-llvm-apple-8.0.0-darwin-macos.tar.gz into /Users/fatin/.konan/dependencies
e: java.lang.RuntimeException: Cannot extract archive with dependency: /Users/fatin/.konan/cache/clang-llvm-apple-8.0.0-darwin-macos.tar.gz.

> Task :shared:compileKotlinIosX64 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':shared:compileKotlinIosX64'.
> Compilation finished with errors

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 7s
1 actionable task: 1 executed
Command PhaseScriptExecution failed with a nonzero exit code ```
[![enter image description here][3]][3]

Mac OS X app - deploying to Applications directory

noemail@noemail.org (davis) — Mon, 3 Aug 2015 18:16:54 GMT

I'm trying to have my app deploy to a user's applications directory on install, but am having trouble determining the correct configuration settings.

Right now I have:

Deployment Postprocessing - YES Installation Build Products Location - "" Installation Directory - "/Applications"

This seems to work when doing xcodebuild install, but is this the best way to do this? I had to change Installation Build Products Location from /tmp/Project.dst to an empty string which doesn't seem right. Also should these settings be set on the target, the project, or both?

Is it possible to customize the indent style of XCode?

noemail@noemail.org (Paul Wicks) — Tue, 23 Jun 2009 21:32:16 GMT

For example, I'd like to not indent namespaces in C++ code, but the prefpane doesn't seem to have any place to make a decision of this granularity. Is there some hidden config file or something? Or am I just out of luck?

Run unit test of a Package from Host application project

noemail@noemail.org (Kaunteya) — Sat, 12 Apr 2025 08:44:40 GMT

I have moved some logic of my app to a separate framework. I am adding it as a local package. How do I run the unit tests of the framework alongside the host apps unit test?

How to correctly install Admob into my Swiftui project?

noemail@noemail.org (Jason W) — Mon, 20 Apr 2026 14:50:39 GMT

New to SwiftUI and I am working on my first game. I have been following the instructions from this YouTube video to add Admob to the project:

https://www.youtube.com/watch?v=ZPGvJmw2xfc

Below is the problematic code from the video that appears to be out of date (maybe):

func load() {
        
        let request = Request()
        
        InterstitialAd.load(with: adUnitID, request: request){ [weak self] ad, error in
            if let error { print("Failed to load \(error)"); return}
            self?.interstitial = ad
            self?.interstitial?.fullScreenContentDelegate = self
            print("interstitial has loaded!!!")
        }
    }
    
    func present() {
        guard let root = UIApplication.shared.firstKeyWindowRootViewController() else {return}
        guard let interstitial else {
            print("Not Ready! Loading now!") ; load() ; return
        }
    }

WARNING: I get a warning for this code:

self?.interstitial?.fullScreenContentDelegate = self

The warning is:

Main actor-isolated conformance of 'InterstitialAdManager' to 'FullScreenContentDelegate' cannot be used in nonisolated context; this is an error in the Swift 6 language mode

ERROR - I get an error for this code:

guard let root = UIApplication.shared.firstKeyWindowRootViewController() else {return}

The error is:

Value of type "UIApplication' has no member 'firstKeyWindowRootViewController

I'm not sure how to resolve the warning or the error.

Below is the rest of the code from the video if it helps, no errors or warnings appear in the remainder. I did add the package dependencies for Google Mobile Ads to the project.

import SwiftUI
import GoogleMobileAds
import Combine
import Foundation


final class InterstitialAdManager:NSObject, ObservableObject, FullScreenContentDelegate {
    
    private let adUnitID = "ca-app-pub-3940256099942544/1033173712"
    
    private var interstitial: InterstitialAd?
    
    func load() {
        
        let request = Request()
        
        InterstitialAd.load(with: adUnitID, request: request){ [weak self] ad, error in
            if let error { print("Failed to load \(error)"); return}
            self?.interstitial = ad
            self?.interstitial?.fullScreenContentDelegate = self
            print("interstitial has loaded!!!")
        }
    }
    
    func present() {
        guard let root = UIApplication.shared.firstKeyWindowRootViewController() else {return}
        guard let interstitial else {
            print("Not Ready! Loading now!") ; load() ; return
        }
    }
    
    
    func adDidDismissFullScreenContent(_ ad: any FullScreenPresentingAd) {
        print("Dismissed, loading next ad!")
        self.interstitial = nil
        self.load()
    }
    
    
    func ad(_ ad: FullScreenPresentingAd, didFailToPresentFullScreenContentWithError error: Error) {
        print("Failed to present \(error)")
        self.interstitial = nil
        self.load()
    }
    
}



private extension UIApplication {
    func firstKeyWindowRootViewContoller() -> UIViewController? {
        connectedScenes
            .compactMap { ($0 as? UIWindowScene)?.keyWindow}
            .first?
            .rootViewController
    }
}


private extension UIWindowScene {
    var keyWindow:UIWindow? { windows.first(where: { $0.isKeyWindow})}
}

How to remove "cannot use default expression for inference" warning when trying to make @ViewBuilder closure with parameters optional?

noemail@noemail.org (Ser Pounce) — Mon, 20 Apr 2026 07:56:39 GMT

I have a common pattern in my app where I define a @ViewBuilder closure in a generic Struct in such a way that it's optional to be used:

struct MenuList<T: MenuListItem, AdditionalRowActions: View>: View
{
    private var additionalRowActions: (T, Binding<Bool>) -> AdditionalRowActions
    
    init(@ViewBuilder additionalRowActions: @escaping (T, Binding<Bool>) -> AdditionalRowActions = { (_: T, _: Binding<Bool>) in EmptyView() })
    {
        self.additionalRowActions = additionalRowActions
    }
}

After I installed Xcode 26.4, I'm now getting a warning on the parameter that says:

Cannot use default expression for inference of '(T, Binding<Bool>) -> AdditionalRowActions' because it is inferrable from parameters #0, #12, #13, #17, #18, #20, #21, #22, #24, #25; this will be an error in a future Swift language mode

The properties referenced (which I omitted from the initial example for brevity) all are of type T, [T], or a non @ViewBuilder closure that takes T as a parameter.

I'm wondering if anyone knows what I can do to get rid of this warning while maintaining the same functionality?

"Use of private header from outside its module:" in a Cocoapods dependency in an Xcode project

noemail@noemail.org (user27192979) — Fri, 3 Apr 2026 09:10:37 GMT

Some background, in our iOS project we have a dependency on RestKit, an outdated networking and request mapping library. It has its own dependency on AFNetworking, another outdated library, but it has vendored the files in a subfolder (so no versioning on that at all). Since iOS 26 it has been giving an error in the file RestKit/Network/AFHTTPClient.m namely:

"Use of private header from outside its module: 'netinet6/in6.h'"

I have tried dealing with this in several ways. The first thought was to simply remove the offending line, this works and no other errors pop up. However the included file defines a bunch of constants related to networking that I prefer not to change without understanding them first. The inclusion also depends on _SYSTEM_CONFIGURATION being defined, so I figured if I can somehow configure the build to not define that, it will skip including the header with no changes to the code. This define seemingly controls the addition of reachability to the framework, which we don't use through this library, so it would be fine to miss that functionality. Finally, the header is a system header and I'm almost certain there must be a way to include it anyway, albeit with specific build parameters.

When I remove the line, everything seems to work fine. So any confirmation/explanation that it's fine to remove would be an acceptable answer. The file also includes netinet/in.h and there seems to be logic to prevent including netinet6/in6.h directly. This could very well be an incorrect include regardless of iOS 26.

It seems the _SYSTEM_CONFIGURATION define is added when the optional SystemConfiguration framework is included, removing it does get rid of the error when building standalone, but not when including the dependency in the project. A reproducible way of removing that framework that keeps the error away even in the project that includes this lib would also be an acceptable answer.

I have also tried to wrestle with the modulemap for a bit. Technically I should be able to tell clang that it's all good by configuring the modulemap file, but I'm not versed enough in clang's syntax and options to come up with a fix. A working modulemap example that I can use to get rid of the error would also be acceptable as an answer. I read that when the library is a system framework it should be allowed, but Xcode is not having it, spitting out more errors about the invalid modulemap on top of the original error.

I am currently investigating disabling the error with -Wno-private-header, but I can't seem to get it to work. Either I'm using the wrong flags fields or the option doesn't work to disable this error.

On the off chance someone knows of a good replacement, that would also be acceptable. But I've looked to replace this thing many times before and our equally outdated API format being JSON-like but not quite valid JSON makes this one of the only working solutions for mapping our entities (which is all we use it for, really).

What is the best approach?

Restkit:
https://github.com/restkit/restkit
Offending file:
https://github.com/RestKit/RestKit/blob/development/Code/Network/AFNetworking/AFRKHTTPClient.m

AFNetworking (original, also has the problem):
https://github.com/AFNetworking/AFNetworking

Invalid bundle - on iPad, you need to include the Main.storyboard launch storyboard file in your bundle

noemail@noemail.org (viral goti) — Wed, 15 May 2024 10:18:35 GMT

I have Created one application for mobile using flutter. I uploaded app for google play platform successfully. After that I uploaded app for iPhone AppStore through Xcode it gives error like belove

"Invalid bundle. Because your app supports Multitasking on iPad, you need to include the Main.storyboard launch storyboard file in your bundle. Use UILaunchScreen instead if the app’s MinimumOSVersion is 14 or higher and you prefer to configure the launch screen without storyboards. For details, see: https://developer.apple.com/documentation/bundleresources/information_property_list/uilaunchstoryboardname (ID: - - -)"

I am not able to solve this issue. So, I just remove iPad option from Xcode and public only for iPhone device.

How would you trace back the source of an imported framework?

noemail@noemail.org (Dave Verwer) — Tue, 15 Oct 2013 10:12:51 GMT

With Xcode 4 and the iOS 6 SDK in order to make use of the classes in QuartzCore.framework you had to link against the QuartzCore.framework and #import <QuartzCore/QuartzCore.h>. This was fine and it made sense. I was happy with my view of the world :)

In Xcode 5 with the iOS 7 SDK the QuartzCore headers seem to be getting imported automatically. Using CA classes raises no warnings or linker errors.

My question is this:

Given that these headers are obviously being imported from somewhere and the library is being linked, how do I trace the source of the import and the linked framework? This is more just for my curiosity and to understand more about this process than to solve a specific problem.

Additional Information:

Modules are switched on (by default in Xcode 5) but @import is not being used in any of the code. However, switching Enable Modules (C and Objective-C) and Link Frameworks Automatically both to be "No" does not seem to require the #import of QuartzCore to compile.
Once modules are switched off, viewing Product | Perform Action | Preprocess shows the QuartzCore header in the preprocessed output. This explains why the code compiles, but not where it came from.

otool shows nothing of the QuartzCore framework in its output:

$ otool -L Test 
Test:
    /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics (compatibility version 64.0.0, current version 600.0.0)
    /System/Library/Frameworks/UIKit.framework/UIKit (compatibility version 1.0.0, current version 2903.2.0)
    /System/Library/Frameworks/Foundation.framework/Foundation (compatibility version 300.0.0, current version 1047.20.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
    /usr/lib/libSystem.dylib (compatibility version 1.0.0, current version 111.0.0)

Edited with a partial solution

I figured out the source of the #import at least. Checking through the iOS 7 UIKit headers, UISlider now includes an import of <QuartzCore/QuartzCore.h> which was not there in iOS 6. Mystery one solved, but the lack of linker errors is still curious.

Detect if build is triggered from SwiftUI Preview in Build Phases - Run Script

noemail@noemail.org (fer0n) — Fri, 19 Jan 2024 08:54:32 GMT

Is there any way to detect if the build was triggered by the SwiftUI Preview from inside Build Phases - Run Script?

I'm using swiftlint with --fix --format, the problem is when I have the Preview open it sometimes triggers a build, which often changes the file while I'm typing, which then brings up the "keep changes/revert" dialog. Keeping the changes often leads Xcode to crash. Ideally, I'd like to do something like this:

if buildWasTriggeredBySwiftUIPreview then
    swiftlint
else 
    swiftlint --fix --format && swiftlint
fi

Animating launch screen zoom

noemail@noemail.org (TsGDev) — Tue, 12 May 2020 10:36:14 GMT

I'm trying to animate a zoom out/size change of a UIImageView . Below is how I want the launch screen to look and then once it's loaded to go onto my HomeViewController.

Because (at the moment) I'm doing the animation on the HomeViewController which I know isn't the right way to do it, the buttons on my VC instantly appear as the animation is happening

And finally, this is almost how I want it to look, but to achieve this, I've put a UIView which covers the buttons but not the logo and have animated it to fade as if the buttons were fading in.

So how would I do the initial animation on the launch screen before loading my HomeViewController? I can't seem to add my UIImageView onto my AppDelegate.swift to do the animation there, many thanks!

CODE: (in viewDidLoad of HomeViewController)

let orginalY = self.imageView.center.y
    UIView.animate(withDuration: 1.0, animations: {() -> Void in
        self.imageView?.transform = CGAffineTransform(scaleX: 0.5, y: 0.5)
        self.imageView.center.y = orginalY - 100
    }, completion: nil)

    UIView.animate(withDuration: 1.2) {
        self.hidingView.alpha = 0
    }

Simulators don't show up as run destination in Xcode 15.0

noemail@noemail.org (Chris McElroy) — Sun, 1 Oct 2023 16:45:50 GMT

Since upgrading to Xcode 15.0, I have not been able to set simulators as a run destination. They do not show up as an option in the menu (either in the dropdown from the toolbar, or in the Product > Destination menu). However, they do show up in the Devices and Simulators window. They also open happily by themselves (when opening from Xcode > Open Developer Tool > Simulator), but projects still will not recognize them as a possible run destination.

I have tried making many changes, with no luck:

Marking several simulators to 'always' show up, instead of automatically
Making new, custom simulators
Including both architectures under Product > Destination > Destination Architectures
Deleting and redownloading my copy of iOS 17
Running new or pre-existing projects
Running iOS only and multi-platform projects
Restarting Xcode and restarting my computer

Xcode will connect and run apps on my phone (iPhone 14 Pro running iOS 17.01). Interestingly, the canvas for SwiftUI says "Loading iOS 17.0...", but it never actually loads (though it will preview on my phone). I would think this points to an issue with my iOS 17 download, but the simulators seem to boot just fine. Many of these attempted fixes were inspired by answers to this similar question.

Running xcrun simctl list yields a long list of simulators:

== Device Types ==
iPhone 6s (com.apple.CoreSimulator.SimDeviceType.iPhone-6s)
iPhone 6s Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-6s-Plus)
iPhone SE (1st generation) (com.apple.CoreSimulator.SimDeviceType.iPhone-SE)
iPhone 7 (com.apple.CoreSimulator.SimDeviceType.iPhone-7)
iPhone 7 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-7-Plus)
iPhone 8 (com.apple.CoreSimulator.SimDeviceType.iPhone-8)
iPhone 8 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus)
iPhone X (com.apple.CoreSimulator.SimDeviceType.iPhone-X)
iPhone Xs (com.apple.CoreSimulator.SimDeviceType.iPhone-XS)
iPhone Xs Max (com.apple.CoreSimulator.SimDeviceType.iPhone-XS-Max)
iPhone Xʀ (com.apple.CoreSimulator.SimDeviceType.iPhone-XR)
iPhone 11 (com.apple.CoreSimulator.SimDeviceType.iPhone-11)
iPhone 11 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro)
iPhone 11 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max)
iPhone SE (2nd generation) (com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-)
iPhone 12 mini (com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini)
iPhone 12 (com.apple.CoreSimulator.SimDeviceType.iPhone-12)
iPhone 12 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro)
iPhone 12 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max)
iPhone 13 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-13-Pro)
iPhone 13 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-13-Pro-Max)
iPhone 13 mini (com.apple.CoreSimulator.SimDeviceType.iPhone-13-mini)
iPhone 13 (com.apple.CoreSimulator.SimDeviceType.iPhone-13)
iPhone SE (3rd generation) (com.apple.CoreSimulator.SimDeviceType.iPhone-SE-3rd-generation)
iPhone 14 (com.apple.CoreSimulator.SimDeviceType.iPhone-14)
iPhone 14 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-14-Plus)
iPhone 14 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-14-Pro)
iPhone 14 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-14-Pro-Max)
iPhone 15 (com.apple.CoreSimulator.SimDeviceType.iPhone-15)
iPhone 15 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Plus)
iPhone 15 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro)
iPhone 15 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro-Max)
iPod touch (7th generation) (com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-)
iPad mini 4 (com.apple.CoreSimulator.SimDeviceType.iPad-mini-4)
iPad Air 2 (com.apple.CoreSimulator.SimDeviceType.iPad-Air-2)
iPad Pro (9.7-inch) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-)
iPad Pro (12.9-inch) (1st generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro)
iPad (5th generation) (com.apple.CoreSimulator.SimDeviceType.iPad--5th-generation-)
iPad Pro (12.9-inch) (2nd generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---2nd-generation-)
iPad Pro (10.5-inch) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--10-5-inch-)
iPad (6th generation) (com.apple.CoreSimulator.SimDeviceType.iPad--6th-generation-)
iPad (7th generation) (com.apple.CoreSimulator.SimDeviceType.iPad--7th-generation-)
iPad Pro (11-inch) (1st generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch-)
iPad Pro (12.9-inch) (3rd generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---3rd-generation-)
iPad Pro (11-inch) (2nd generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch---2nd-generation-)
iPad Pro (12.9-inch) (4th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---4th-generation-)
iPad mini (5th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-mini--5th-generation-)
iPad Air (3rd generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Air--3rd-generation-)
iPad (8th generation) (com.apple.CoreSimulator.SimDeviceType.iPad--8th-generation-)
iPad (9th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-9th-generation)
iPad Air (4th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Air--4th-generation-)
iPad Pro (11-inch) (3rd generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro-11-inch-3rd-generation)
iPad Pro (12.9-inch) (5th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro-12-9-inch-5th-generation)
iPad Air (5th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Air-5th-generation)
iPad (10th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-10th-generation)
iPad mini (6th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-mini-6th-generation)
iPad Pro (11-inch) (4th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro-11-inch-4th-generation-8GB)
iPad Pro (11-inch) (4th generation) (16GB) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro-11-inch-4th-generation-16GB)
iPad Pro (12.9-inch) (6th generation) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro-12-9-inch-6th-generation-8GB)
iPad Pro (12.9-inch) (6th generation) (16GB) (com.apple.CoreSimulator.SimDeviceType.iPad-Pro-12-9-inch-6th-generation-16GB)
Apple TV (com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p)
Apple TV 4K (com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K)
Apple TV 4K (at 1080p) (com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p)
Apple TV 4K (2nd generation) (com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-2nd-generation-4K)
Apple TV 4K (2nd generation) (at 1080p) (com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-2nd-generation-1080p)
Apple TV 4K (3rd generation) (com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-3rd-generation-4K)
Apple TV 4K (3rd generation) (at 1080p) (com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-3rd-generation-1080p)
Apple Watch Series 2 (38mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-38mm)
Apple Watch Series 2 (42mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-2-42mm)
Apple Watch Series 3 (38mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-38mm)
Apple Watch Series 3 (42mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-3-42mm)
Apple Watch Series 4 (40mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-40mm)
Apple Watch Series 4 (44mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-44mm)
Apple Watch Series 5 (40mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-40mm)
Apple Watch Series 5 (44mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-44mm)
Apple Watch SE (40mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-SE-40mm)
Apple Watch SE (44mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-SE-44mm)
Apple Watch Series 6 (40mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-40mm)
Apple Watch Series 6 (44mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-44mm)
Apple Watch Series 7 (41mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-7-41mm)
Apple Watch Series 7 (45mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-7-45mm)
Apple Watch SE (40mm) (2nd generation) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-SE-40mm-2nd-generation)
Apple Watch SE (44mm) (2nd generation) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-SE-44mm-2nd-generation)
Apple Watch Series 8 (41mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-8-41mm)
Apple Watch Series 8 (45mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-8-45mm)
Apple Watch Ultra (49mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Ultra-49mm)
Apple Watch Series 9 (41mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-9-41mm)
Apple Watch Series 9 (45mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-9-45mm)
Apple Watch Ultra 2 (49mm) (com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Ultra-2-49mm)
== Runtimes ==
iOS 17.0 (17.0 - 21A328) - com.apple.CoreSimulator.SimRuntime.iOS-17-0
== Devices ==
-- iOS 17.0 --
    iPhone SE (3rd generation) (C9B93C6E-6F5C-4885-A1B5-FBDCBB31C462) (Shutdown)
    ez (196EDFD8-C5A9-45A5-A7AC-2B39E07055B8) (Shutdown)
    iPhone 15 (857F0720-4BE4-40B6-A755-D38E1E53608F) (Shutdown)
    iPhone 15 Plus (3936179C-96B4-4947-A6C6-883130058909) (Shutdown)
    iPhone 15 Pro (89F1FBF8-5A76-4E94-B948-3DACCBF7AFBF) (Shutdown)
    iPhone 15 Pro Max (BADA1F50-197A-4FD0-89CF-1F8F10B99149) (Shutdown)
    iPad Air (5th generation) (217163A8-1FA1-4E96-BC9C-8BA436A4E880) (Shutdown)
    iPad (10th generation) (A6820111-FDF8-4EA3-B573-FDDD72D5A0A6) (Shutdown)
    iPad mini (6th generation) (19DA9216-4EC7-4DD8-9688-840C8A3FE8B4) (Shutdown)
    iPad Pro (11-inch) (4th generation) (D1BFB2C4-C752-452A-B700-730FBC8D2EAA) (Shutdown)
    iPad Pro (12.9-inch) (6th generation) (87322B2B-FD56-4B07-B254-B61816E33B83) (Shutdown)
== Device Pairs ==

My computer is a MacBook Pro M1 Pro running Ventura 13.6. I'm hesitant to update to Sonoma before resolving this issue.

iOS : Testflight No build available for external testers

noemail@noemail.org (Hardik Amal) — Mon, 25 Jun 2018 11:54:20 GMT

I am using testflight as a beta testing tool for my app. I have uploaded the build but invitation are successfully sent to the internal testers but no invitations are sent to external tester.

Below image shows both the groups has been invited

And this image shows that no build available for external testers

Can anyone help me how I can get through with this?

Xcode documentation has disappeared

noemail@noemail.org (tmlen) — Wed, 15 Apr 2026 19:47:08 GMT

I'm using Xcode 26.4 for Swift development on macOS 26.4.1.

It seems that the documentation for the "Foundation" framework has disappeared, possibly after an Xcode update (not the latest one). "Foundation" does not appear in the left-side list in the developer documentation window, and searching for "URLSession", "UndoManager" finds no result.

Autocomplete for these classes works. Quick help on URLSession shows just "inherits from" and "conforms to", but no description and no link to a help page.

I've tried deleting files in ~/Library/Developer so that it rebuilds the index, and also fully removing and reinstalling Xcode and rebooting, but nothing seems to solve it.
Is there any way to get the full documentation back in Xcode.

Xcode Preview crash with ModelContainer initialization

noemail@noemail.org (Tony Chen) — Wed, 24 Dec 2025 16:54:31 GMT

Background:

I have complex Swift Data models with some Relationships, and at some point, my Xcode Preview is no longer working when I want to init a ModelContainer in it. So I tried to debug and create a simple file with no dependencies with other parts of my project.

Here's my simple code:

import Foundation
import SwiftUI
import SwiftData

struct DebugView: View {
    var body: some View {
        Text("Hello")
    }
}

@Model
class User {
    var name: String

    init(name: String) {
        self.name = name
    }
}

#Preview {
    let config = ModelConfiguration(UUID().uuidString, isStoredInMemoryOnly: true)
    let container = try! ModelContainer(for: User.self, configurations: config) // This line failed
    DebugView()
}

The thing is even this simple view cannot be shown in the Preview window. Error message:

I'm sure that the crash line is at the ModelContainer init because it works fine without it.

I tried to delete the cache data with command:

xcrun simctl --set previews delete all

But it's still not working.

The weird thing is, when I created a new project and move all the files in it, it works at the beginning. But it started to failed when I tried to do some modifications on other files (these simple codes stay unchanged).

Does any one have any idea?

Can one determine the iOS SDK version used to build a binary, programmatically, at run time?

noemail@noemail.org (Michael Tyson) — Thu, 28 Aug 2014 03:14:08 GMT

Ah, iOS 8 - lots of unexpected changes from iOS 7 to account for!

tl;dr: Is there a way to programmatically determine the iOS SDK version used to build an app, at run-time (not with a preprocessor macro)?

I'm struggling with some window frame calculations for a library I maintain (distributed as a pre-built static library), as iOS 8 has changed the way the screen coordinate system works.

Two initial observations, running code for iOS 7 with no changes for iOS 8:

When built with the iOS 7 SDK, and run on iOS 8, everything works as prior, no changes necessary.
When built with the iOS 8 SDK, and run on iOS 8, it's broken: some changes in frame calculation are needed to get correct positioning.

So, we change the code, with conditionals on [[UIDevice currentDevice] systemVersion], to work correctly with the new coordinate system. Now:

When built with the iOS 7 SDK, and run on iOS 7, everything works.
When built with the iOS 8 SDK, and run on iOS 8, everything works.

BUT:
When built with the iOS 7 SDK, and run on iOS 8, the calculations are off - remember, when built with the iOS 7 SDK, everything worked fine prior to the iOS 8-specific code changes. So, the changes made actually broke stuff.

Now, normally, I could happily solve this with some macro conditionals on the SDK version (#ifdef __IPHONE_8_0, etc). But I'm distributing a pre-built static library, built with the iOS 7 SDK, so the code within those conditionals would never make it in. Here's why that's a problem:

If the static library is built with the iOS 7 SDK, but linked into an app built with the iOS 8 SDK, it's the same as if the static library were built with the iOS 8 SDK (because the linking happens at the final app compilation stage, of course). That means I need to have those iOS 8 changes in there, when the app is built with the iOS 8 SDK -- but I can't use a macro conditional to determine whether to use them, as the C preprocessor did its thing during the static library build under iOS 7.

So, my question is this: does anyone know how I might be able to determine whether the app build was made with the iOS 8 SDK, at runtime, from within the pre-compiled static library?

I did try checking for an iOS 8-only SDK feature (-[UIScreen nativeBounds], for example), but that doesn't fly -- the symbol's available regardless of SDK version.

Anyone have any ideas?