So I'm tryin to install an blank application on my device but It doesn't show on the Run on Target in Xcode, but when I look at manage run destination it shows my device?
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
We have some third-party SDKs do not support arm64 simulator, so we excluded arm64 for Any iOS Simulator SDK in Excluded Architectures. But in this case, ASWebAuthenticationSession will display abnormally.
We submitted FB14853757 during the beta period, but have not received any response. This issue still exists in the official version. I hope it can be resolved. Thank you!
Error collecting extracted types: The file “SmartPlusWidgetControl.swift” couldn’t be opened because the text encoding of its contents can’t be determined.
Topic:
Developer Tools & Services
SubTopic:
Xcode
We are using a workspace file and have noticed that when we run fastlane commands that utilize xcodebuild command line arguments to run the export localization command from commandline, and it seems that it uses the xcodeproj package.resolved instead of the workspace package.resolved. This is causing issues as the xcodeproj package resolved will not update at all so is on old version of dependencies that cause xcodebuild commands to fail.
Why is there multiple package.resolved files and why does the xcodeproj not stay updated with what is in the workspace resolved file? Why won't the xcodeproj resolved file update when I'm opening the xcodeproj file and selecting specific dependencies and telling it to update the package.
When AppEnum or AppEntity is introduced into the iOS18 Widget file, xcode compilation will report an error: Error collecting extracted types: The file “SmartPlusWidgetControl.swift” couldn’t be opened because the text encoding of its contents can’t be determined.
Topic:
Developer Tools & Services
SubTopic:
Xcode
I'm facing this issue intermittently since using Xcode 16 beta 4 on macOS 14.5 when starting xcodebuild build with -destination option.
20:56:07 ▸ xcodebuild: error: Unable to find a device matching the provided destination specifier:
20:56:07 ▸ { platform:iOS Simulator, OS:15.4, name:iPhone 13 Pro }
20:56:07 ▸ The requested device could not be found because multiple devices matched the request. (
20:56:07 ▸ "<DVTiPhoneSimulator: 0x151fb1fe0> {\n\t\tSimDevice: iPhone 13 Pro (CB36E92A-C32D-481C-A407-28123ABEBF66, iOS 15.4, Shutdown)\n}",
20:56:07 ▸ "<DVTiPhoneSimulator: 0x151fb4070> {\n\t\tSimDevice: iPhone 13 Pro (0EBBCB9A-5FBA-4998-903B-1415315D1533, iOS 15.4, Shutdown)\n}"
20:56:07 ▸ )
This mac is mac mini 2023 M2 Pro 32GB memory, running with multiple simruntimes installed:
$ sudo xcrun simctl runtime list
Password:
== Disk Images ==
-- iOS --
iOS 17.5 (21F79) - 9FC1CFB3-33A4-4F31-AF40-BAB448F6FA0D (Ready)
iOS 16.4 (20E247) - 3BFB66B1-075B-4B17-951C-B691BAC41C73 (Ready)
iOS 17.2 (21C62) - C8D4111F-1F7A-4FC2-AC6A-BF68A47EEDCE (Ready)
iOS 17.4 (21E213) - 0B8ECC25-EF76-4744-9D77-8256A57D1605 (Ready)
iOS 18.0 (22A5326g) - 7217B9B2-A113-4B6B-915E-CAB70431B415 (Ready)
iOS 17.0.1 (21A342) - C4FE430B-DD3F-4108-B2E7-B13A04989863 (Ready)
iOS 15.4 (19E240) - CAB77B36-B6D3-4F5D-8956-E7A3105AC910 (Ready)
iOS 18.1 (22B5023e) - 9E53F2C6-BA91-421C-848F-F78043179361 (Ready)
-- tvOS --
tvOS 17.2 (21K364) - 8A9929AE-0521-498D-884A-F87BD16612CD (Ready)
tvOS 16.4 (20L494) - 3354C9A4-E177-4030-98F2-0735970E1607 (Ready)
tvOS 17.4 (21L224) - 724CD6DA-EAC2-4076-A578-C84872A36E5E (Ready)
tvOS 15.2 (19K50) - 0AE51520-B1E2-4ED9-80A4-717291FC5E96 (Ready)
tvOS 18.0 (22J5335e) - E839E471-AA01-46E1-A4AD-DF4B98B46525 (Ready)
tvOS 17.5 (21L569) - C432547A-F7EF-4B34-AD43-D3E839CB49E1 (Ready)
tvOS 17.0 (21J353) - 6A08D50B-D9BF-4496-A5C5-FE21373B11DD (Ready)
tvOS 18.0 (22J5324f) - B2C7CA72-AAE6-4DF9-A4B0-26A0EB9462F7 (Ready)
-- watchOS --
watchOS 11.0 (22R5318h) - 56250DF3-CF78-4C5D-B502-0B53DE16ABEB (Ready)
watchOS 10.4 (21T214) - CC71D3D3-EA19-4F0B-BF3E-388D686AB300 (Ready)
watchOS 10.0 (21R355) - 3623992D-88CF-41CB-8091-AF1F8CE16717 (Ready)
watchOS 10.2 (21S364) - C0666241-AA31-4CF7-98B9-EA5394331DC6 (Ready)
watchOS 9.4 (20T253) - EED82B11-589D-41AF-B290-844F59AECECB (Ready)
watchOS 10.5 (21T575) - 0D749B4E-DC69-4F27-8982-510AB985B822 (Ready)
watchOS 8.3 (19S51) - 8123ABC7-5465-4467-A5DA-CE9C50E1081D (Ready)
watchOS 11.0 (22R5328f) - 648646A0-A370-48A4-881B-15B2422DE698 (Ready)
-- xrOS --
xrOS 2.0 (22N5297g) - C2C8E4EE-3738-4706-823E-2B4138CE90BE (Ready)
xrOS 1.0 (21N305) - 29EAB8D4-160D-4A3B-AB7C-7325D205AC4C (Ready)
xrOS 2.0 (22N5286g) - 1F92EE9A-A5F9-45F7-8075-7FD7BC4EF81E (Ready)
xrOS 1.1 (21O209) - DB15F0B2-C9E4-424D-9A50-8D6EDB131142 (Ready)
xrOS 1.2 (21O5565d) - 83A26410-A8A8-41F6-A5A1-E0A7E24B8BA0 (Ready)
I've never seen this kind of simulator missing error.
Nor installing any duplicate runtime(s) on the same machine because it will show error message like 'unable to use this runtime' on xcrun simctl runtime list.
Could anyone give me a tip of avoiding this kind of error?
In Xcode15, I can set the font of the control on the xib to PingFangSC Regular、Medium、Bold, but after upgrading to Xcode16, I can't set the style, only a PingFangSC simplified, how is this?
I'm trying to build an iOS project in command line via xcodebuild.
OS: Mac OS 15.1 beta
Xcode: Xcode 16
Creating a new iOS project and trying to run xcodebuild results in this error. No other dependencies, no frameworks added.
ld: building for 'iOS', but linking in dylib (/Library/Developer/CommandLineTools/SDKs/MacOSX15.0.sdk/usr/lib/libobjc.A.tbd) built for 'macOS macCatalyst zippered(macOS/Catalyst)'
My initial plan was to do this with a VisionOS project, but for some reason, I'm getting errors like this for both platforms and brand new projects.
Any pointers as to what is referencing the MacOS SDK and how I can fix this would be helpful.
Complete log:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk iphoneos -configuration Release -scheme iphonedummy build CODE_SIGNING_ALLOWED=NO -verbose
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
Build settings from command line:
CODE_SIGNING_ALLOWED = NO
SDKROOT = iphoneos18.0
Prepare packages
ComputeTargetDependencyGraph
note: Building targets in dependency order
note: Target dependency graph (1 target)
Target 'iphonedummy' in project 'iphonedummy' (no dependencies)
GatherProvisioningInputs
CreateBuildDescription
// Removed a block for length.
ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -v -E -dM -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk -x c -c /dev/null
// Removed another block for length.
Build description signature: dc5e0c08dfce007b98c7bce87acea5fe
Build description path: /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/XCBuildData/dc5e0c08dfce007b98c7bce87acea5fe.xcbuilddata
ClangStatCache /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang-stat-cache /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/SDKStatCaches.noindex/iphoneos18.0-22A3362-8ec3fe4dca91fa9a941eaa2d5faad0e4.sdkstatcache
cd /Users/sravankaruturi/dev/iphonedummy/iphonedummy.xcodeproj
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang-stat-cache /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk -o /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/SDKStatCaches.noindex/iphoneos18.0-22A3362-8ec3fe4dca91fa9a941eaa2d5faad0e4.sdkstatcache
ProcessInfoPlistFile /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos/iphonedummy.app/Info.plist /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/empty-iphonedummy.plist (in target 'iphonedummy' from project 'iphonedummy')
cd /Users/sravankaruturi/dev/iphonedummy
builtin-infoPlistUtility /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/empty-iphonedummy.plist -producttype com.apple.product-type.application -genpkginfo /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos/iphonedummy.app/PkgInfo -expandbuildsettings -format binary -platform iphoneos -additionalcontentfile /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/assetcatalog_generated_info.plist -requiredArchitecture arm64 -o /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos/iphonedummy.app/Info.plist
Ld /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos/iphonedummy.app/iphonedummy normal (in target 'iphonedummy' from project 'iphonedummy')
cd /Users/sravankaruturi/dev/iphonedummy
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -Xlinker -reproducible -target arm64-apple-ios18.0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk -Os -L/Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/EagerLinkingTBDs/Release-iphoneos -L/Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos -F/Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/EagerLinkingTBDs/Release-iphoneos -F/Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos -filelist /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/Objects-normal/arm64/iphonedummy.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/Objects-normal/arm64/iphonedummy_lto.o -fobjc-link-runtime -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/Objects-normal/arm64/iphonedummy.swiftmodule -Xlinker -dependency_info -Xlinker /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Intermediates.noindex/iphonedummy.build/Release-iphoneos/iphonedummy.build/Objects-normal/arm64/iphonedummy_dependency_info.dat -o /Users/sravankaruturi/Library/Developer/Xcode/DerivedData/iphonedummy-bwpzemojmpkzehhhkxqtjearnxkl/Build/Products/Release-iphoneos/iphonedummy.app/iphonedummy
ld: building for 'iOS', but linking in dylib (/Library/Developer/CommandLineTools/SDKs/MacOSX15.0.sdk/usr/lib/libobjc.A.tbd) built for 'macOS macCatalyst zippered(macOS/Catalyst)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode
Linker
Mac Catalyst
Command Line Tools
Hi there!
Was there a change in Xcode regarding incremental builds / updating an active Simulator with a new build? We use xcodebuild to manage our internal build framework and out of the sudden, incremental builds are not launched anymore and the Simulator is stuck waiting for the new build to be launched. This was not happening for the last 10+ years.
If there is an xcodebuild flag and/or guide of this new behavior, it would help a lot.
Thanks everyone!
我们主要是RN项目,最近进行了mac系统升级,xcode随着升级了,现在版本是16.0
然后,打包RN项目,打包出的ipa从19M增大到了172M,看产物,主要是hermes变大了,
目前导出时候thinning设置的是none,设置thin-for-all-variants后体积会减小,但是会产生多个ipa文件,我们应用是企业内部分发,不上市场的,想咨询一下,这种情况怎么解决?
Hi everyone, sorry if this post comes off odd, I'm on heavy meds
but I intend to do foss gtk development in c on my Mac using Xcode, I've used brew to download the gtk libraries and I've individually added each path to each library for autocorrect and intelligence in Xcode
But when I build a GTK app in Xcode I get a bunch of 'Unresolved Symbol' messages, here's an example:
Undefined symbol: _g_application_get_type
I also get about 460 warnings from various libraries stating:
/opt/homebrew/Cellar/cairo/1.18.2/include/cairo/cairo.h:2773:5 '@callback' command should be used in a comment attached to a pointer to function declaration
I understand that when you need to compile GTK, you need to pass a command to the compiler (in this case pkg-config --libs --cflags gtk4), where in Xcode's project manager do I add that code? I think I'm supposed to run that command and add the output somewhere line by line to a combobox in Xcode, but where? "other linker flags"?
Has anyone had any luck compiling GTK apps directly from Xcode?
Topic:
Developer Tools & Services
SubTopic:
Xcode
I’m using Xcode 16 on an M1 Pro and experiencing overheating issues. It seems like Apple rushed the release without addressing glitches that cause the laptop to overheat, which can directly affect battery life, decreasing its performance and, in turn, lowering the value of the Mac. I really dislike this from Apple. We pay a lot for their products, and issues like these devalue them.
Hello, in the past couple of weeks I've been experience some problems with xcode regarding the signing & capabilities.
I work in a company that makes customized apps for every of our clients and beacause of that we have about 200 targets in our project. In the past couple of weeks, I have been hanving trouble with the signing & capabilities in xcode. Some times is taking too long to load the poart where i select the team were the app will be upload and when it does it got stuck with the massege updating provisioning . There is anything that could have been done to not take too much time to the target get ready to be publiched?
Thanks in advanced for any help.
Hallo Everyone while i try run my app on simulator IPhone 16 Pro Max its come that error (unsupported option '-G' for target 'x86_64-apple-ios10.0-simulator'). Do any one have Idea how to solve it?
Topic:
Developer Tools & Services
SubTopic:
Xcode
The non-async signature for WKNavigationDelegate's decidePolicyForNavigationAction has changed between iOS 17 and 18.
In 17 it is
func webView(_ webView: WKWebView, decidePolicyFor navigationAction: WKNavigationAction, decisionHandler: @escaping (WKNavigationActionPolicy) -> Void)
In 18 it adds the MainActor attribute to the decision handler
func webView(_ webView: WKWebView, decidePolicyFor navigationAction: WKNavigationAction, decisionHandler: @escaping @MainActor (WKNavigationActionPolicy) -> Void)
We deliver xcframeworks to our customers with objects that implement this function, and when those customers upgraded to Xcode 16.0 / iOS 18, those frameworks broke despite ABI stability (since that's unrelated to the WebKit SDK's public signatures). I presume this is because the WebKit dependency in the iOS 18 SDK does not match the signature used those older frameworks (and the IDE errors seem to support this).
We will of course deliver new frameworks targeting the new SDK, but that takes regression testing and release planning. In the meantime, this has been exacerbated by the fact that macOS Sequoia does not support Xcode 15. Those of our customers whose machines updated to Sequoia cannot build their projects at all until we're able to deliver frameworks that are compatible.
Was this an expected change? I didn't see any deprecation warnings in iOS 17, and unless we're supposed to bundle WebKit within the framework somehow, I'm not sure how we could have done this without forcing the Xcode versioning on our customers.
Is there a way we package this differently or some other solution to make our existing frameworks compatible with iOS 18 without having to target that SDK?
Mac OS: 12.3.1 Monterey (Mac Mini 202
Xcode: 13.4.1
'xcodebuild -version' hangs indefinitely for most users, except for one local admin account and one non-admin account (LDAP user). I've searched high and low and found some related issues on this forum and elsewhere, most of which indicate that the Xcode license has not been accepted and provide instructions to accept it from the command line. All of these have been tried countless times, plus Xcode 13.4.1 and CommandLineTools have been reinstalled, and still the issue remains: Only one non-admin user (myself) and the local admin user can run 'xcodebuild' from the command line without hanging. The same is true from Mac Terminal application in a remote console (VNC) session, or putty/xterm connected remotely via ssh.
We can't upgrade Mac OS or Xcode as this is a build/test machine in a server farm and the specific OS and Xcode versions are required minimums for customer support purposes.
Doesn't seem that there is setting unique to each user that could enable/disable Xcode, but the inner workings of Mac OS and Xcode remain largely a mystery.
Please help!
Topic:
Developer Tools & Services
SubTopic:
Xcode
New install of Xcode 16 seemed fine initially. However I've noticed that File > Open Recent is now empty and won't populate at all no matter what projects I open and close etc.
Any ideas how to fix this?
TIA
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hi,
I'm looking for some advise how to narrow down the location of the crash.
When I run the app with Debug configuration (GCC_OPTIMIZATION_LEVEL=0) everything just works. But in Release configuration with -Os the app crashes. Also need to mention that the crash happens on the device only, but not on the simulator. When the crash happens, there's no stack trace available. The crash happens every time, a couple seconds after I see the first screen. Currently I'm using Xcode Version 16.0 (16A242d), but I have also tried all combinations of:
Xcode 16.1 Beta 1
Xcode 16.1 Beta 2
Device with iOS 18
Device with iOS 17.7
Device with iOS 17.6.1
The result is always the same.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=257, address=0x100000002)
* frame #0: 0x0000000100000002
Is there anything I can do to further narrow down the location of the crash?
Here's a full crash report that I got from the device: https://gist.github.com/plu/e9ed984f438358b5fbf120148cbbaef0
Since I updated my Xcode to Xcode 16 my app is constantly shutting down with "App is Crashing with "Message from debugger: Terminated due to signal 6"without any other errors or exceptions.
Any thoughts?
Topic:
Developer Tools & Services
SubTopic:
Xcode
On my mac I have MacOs15 and Xcode 16 installed. I'm working with cocoapods, when adding a new target to my App pod update it fails. What can I do to solve the problem?
Topic:
Developer Tools & Services
SubTopic:
Xcode