Hello I have a problem with provisionprofile file. I have created Identifier with Sign in with Apple capability turned on, created Profile with Developer ID selected and now I try to export archive with generated Developer ID provision file but it says "Profile doesn't support Sign in with Apple" Also interesting thing that default provisions like macOS App Development Mac App Store Connect don't show such error when I try to export archive Maybe this problem is only related to Developer ID provision and Direct Distribution doesn't support Sign in with Apple, but I havent found proves about this idea

Where can I find ios 18 DeveloperDiskImage.dmg?

Is there a way in Xcode to change the image viewer to use nearest filtering instead of linear (which I think it uses by default)? I'd like to be able to example exact pixels in my images, similar to I do in the Metal debugger.

Hey guys, so I've read a lot of previous issues opened before opening this one, and I am doing it because none of the info found solved my problem. So, I am trying to build my app which it has a custom Info.plist file. But i keep getting the issue of multiple command when trying to build. Here is how it;s configured: Info.plist has the target membership correct Build Setting is set to 'NO' under "Generate Info.plist File" The path is correct, in the same folder as the ContentView And here is what I've already tried to fix the issue: Check in Build Phases if the wasn't a duplication: There isn't Removing the Info.plist from the "Copy Bundle Resources": When I do this, than I get another issue which is "Build input file cannot be found. Did you forget to declare this file as an output of a script phase or custom build rule which produces it?" Switching the Build to Legacy Build System: Nothing changed Deleting the manually created Info.plist file and changing the Build Settings to 'YES' under "Generate Info.plist File": I get the same issue "Build input file cannot be found. Did you forget to declare this file as an output of a script phase or custom build rule which produces it?" Deleted the Derived Data multiple times Deleted the Info.plist file and re-added it through File > New File Anyway, this is my last resource to find some help here in the forum. Any insight is valid P.S: XCode version 16.1

Since updating to macOS Sequoia, I see this dialog every time I launch my SwiftUI macOS app from Xcode: Users who installed the app from the App Store don’t see it. And this didn’t happened in previous macOS versions. Could launching it from Xcode be triggering some extra access requirement? How can I stop this dialog from appearing every time I launch my app? It’s very disruptive to the debugging process.

Hello community! Recently I faced unusual problem when I'm trying to run UITest from commandline. Everything works from XCode (I can execute UITest on both simulator and device), but in console I'm always getting: xcodebuild: error: Unable to find a destination matching the provided destination specifier: { platform:iOS Simulator, OS:17.5, name:iPhone 15 Pro } I already checked lot of possible solutions but none worked. What seems to be important here, I don't have any "Available destinations" proposal. Also installed XCode version is 16, but I need to run this project on 15.4 which is in another folder (I used xcode-select to choose 15.4, also tried to execute xcodebuild using full path) . Executing: xcrun simctl list shows me f.e.: -- iOS 17.5 -- iPhone 13 Pro (D20DE861-B938-4FD3-9797-F0AE0BBA5569) (Shutdown) iPhone 15 (FE8687E4-B7CD-4861-83F8-B9E833F14982) (Shutdown) iPhone 15 Plus (4B1F46CC-7C95-496B-9776-EC6BC539199E) (Shutdown) iPhone 15 Pro (C622866E-74C8-45F5-A7B0-DFA76BC7C452) (Booted) iPhone 15 Pro Max (CEF3892C-CFD4-4558-A317-A6EBDB079AAF) (Shutdown) but running: xcodebuild -workspace ./***.xcworkspace -scheme xxxUITests -destination 'platform=iOS Simulator,name=iPhone 15 Pro,OS=17.5' build brings same error. What is also interesting, I'm getting same error when trying to run same command in GitLab pipeline. Is there anyone who had same problem?

I've discovered a bug in Xcode 16.0/16.1 where using std::variant in containers across compilation units triggers UBSan errors. This is a regression as it works correctly in Xcode 15.4. Here's a minimal reproduction case: [base.h] #pragma once #include <string> #include <variant> #include <forward_list> class Item { public: std::variant<std::monostate, std::string> value; }; typedef std::forward_list<Item> ItemList; class Test { public: void addItem(const Item& item); ItemList items; }; [base.cpp] #include "base.h" void Test::addItem(const Item& item) { items.push_front(item); } [main.cpp] #include "base.h" int main() { Test t; Item item; t.addItem(item); return 0; } To reproduce: Compile with UBSan enabled (-fsanitize=undefined) Occurs on both arm64 and x86_64 Occurs in both Xcode 16.0 and 16.1 Works correctly in Xcode 15.4 I've filed a Feedback Assistant report: FB15710420 Workaround: The issue can be avoided by implementing the addItem method in the header file instead of a separate compilation unit. Has anyone else encountered this issue? Are there other workarounds besides moving the implementation to the header?

Hello everyone, I’m currently developing my first VisionOS app in Xcode, starting with the default "Hello World" code provided when creating a new VisionOS Mixed Reality App. However, I’m facing some issues with performance and previewing that I can’t seem to resolve. When I load the preview, it takes an extremely long time, and sometimes it doesn’t load at all. Even when I try to run the app in the VisionOS Simulator, the simulator shows an endless black screen and never displays the intended view. I’ve made no changes to the code, so it’s purely the base setup. Here are my system details: Xcode version: 16.1, VisionOs 2.0; macOS version: 15.0.1; Hardware: MacBook Air 2020 M1 I’ve tried restarting Xcode and my machine, but the issue persists. Has anyone else faced similar problems or have any suggestions for fixing this? Or is my hardware simply too weak? Any help would be greatly appreciated! Thank you in advance!

For new iOS apps you can select Swift or Objective-C but you cannot choose Objective-C for new watchOS apps. A new watchOS app is always Swift. Any help would with selecting Objective-C for new watchOS apps would be greatly appreciated.

I noticed that IBDesignable was deprecated in the Xcode 16 release notes, and IBInspectable was deprecated in the Xcode 16.1 release notes. So, I performed some tests on IBDesignable and IBInspectable in Xcode. I wrote the following code: @IBDesignable extension UIView { @IBInspectable var cornerRadius: CGFloat { get { layer.cornerRadius } set { layer.cornerRadius = newValue } } @IBInspectable var borderWidth: CGFloat { get { layer.borderWidth } set { layer.borderWidth = newValue } } @IBInspectable var borderColor: UIColor { get { UIColor(cgColor: layer.borderColor ?? .init(red: 1, green: 1, blue: 1, alpha: 0)) } set { layer.borderColor = newValue.cgColor } } } I cannot access the IBInspectable property in Xcode 16. However, I can access the IBInspectable property in Xcode 16.1 and Xcode 16.2 Beta, where the Interface Builder shows it in the Attributes Inspector. Is it possible that this will be updated later, as it differs from the release notes? Thank you.

I ran out of disk space and I think I've come to the point that I need to delete files used by Xcode. Can I delete Simulator altogether? It doesn't look like I can run the latest Xcode without iOS 18 installed with it on my Mac Pro. Is there any way I can exclude iOS 18 support using the current Xcode? Would it be a good option to uninstall the latest Xcode and use a previous version of Xcode instead, since I'm not developing for iOS 18? Since I've been working on only macOS apps, is it possible for me to delete anything that has to do with developing for iOS?

This bundle is invalid. Unable to load ‘Info.plist’ for bundle at path: ‘My App.app/Contents/Library/Spotlight/MyApp-SpotlightIndex.mdimporter’.. This mdimporter is embedded in my app with a Copy step in Build Phases and when I Archive the compiled app, I get that error when I try to Validate. The app works OK, the mdimporter Spotlight works OK, all runs fine. But the Validate on the Archive does not work, it fails with that error.

I have to guess which command queue is the one I want to debug in Xcode here: I have label set, but it doesn't seem to affect this part of Xcode.

I believe starting from version 15, Developer Documentation is broken in several ways (at least for me). Quick Help pane shows meaningless header information about many classes: Reveal in Navigator does not work in most cases: For example stringWithFormat:

When developing with SwiftUI, I encountered the following error: failed to produce diagnostic for expression; please submit a bug report (https://swift.org/contributing/#reporting-bugs) Since I don’t understand the reason behind this error, what details should I include in the report?

Hi, I try to add the Firebase requirements to my iOS application. I launched the package manager, at first, nothing was loading, therefore I deleted and recreated my Github account, and the previous packages now appears. When I try to paste the url for Firebase in the search bar, there is an infinite loading loop and it never appears. I tried to restart Xcode several times, to disconnect and reconnect from wifi etc. Can anyone help me solve this please?

Since updating to Xcode 16.1, the software crashes every time I try to load a .storyboard file in Interface Builder. Has anyone encountered this issue or can offer assistance?

Could someone help me with a good direction on where or how could I fix for this crash from console log: Not able to open storyboard or XIB. Once opening them, Xcode is crashing. tried uninstalling the Xcode, couldn't fix even after deleting derived data and caches. ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Incident Identifier: 7E6D64FF-D4E9-4E3A-A37A-BC5016316DCD CrashReporter Key: 4776E37C-4D3D-F705-40D5-8A96EE95C89A Hardware Model: Mac15,6 Process: IBAgent-iOS [31688] Path: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Overlays/IBAgent-iOS Identifier: IBAgent-iOS Version: 16.0 (23506) Code Type: ARM-64 (Native) Role: Unspecified Parent Process: launchd_sim [31680] Coalition: com.apple.CoreSimulator.SimDevice.178E8D7E-176F-4B7F-8956-D26C5EF7323A [5165] Responsible Process: SimulatorTrampoline [1185] Date/Time: 2024-11-06 14:59:29.3079 +0530 Launch Time: 2024-11-06 14:59:28.9368 +0530 OS Version: macOS 15.1 (24B83) Release Type: User Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000102e1e19c Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [31688] Triggered by Thread: 0 Application Specific Information: Abort Cause 259 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x102e1e19c _os_unfair_lock_recursive_abort + 36 1 libsystem_platform.dylib 0x102e19504 _os_unfair_lock_lock_slow + 304 2 libGSFont.dylib 0x19045ebb4 GSFontFileDescriptorForPath + 28 3 libFontParser.dylib 0x19047d714 TFileDescriptorContext::TFileDescriptorContext(char const*) + 216 4 libFontParser.dylib 0x19057c7e4 TFileDataReference::Map(char const*) + 36 5 libFontParser.dylib 0x19047d514 TFileDataReference::TFileDataReference(char const*) + 88 6 libFontParser.dylib 0x19057c934 TFileDataSurrogate::TFileDataSurrogate(char const*, timespec) + 152 7 libFontParser.dylib 0x1905cbaac TFont::CreateFontEntitiesForFile(char const*, timespec, bool, short, char const*) + 580 8 libFontParser.dylib 0x19047d1e0 FPFontCreateFontsWithPath + 200 9 CoreGraphics 0x18b612c54 create_private_data_array_with_path + 16 10 CoreGraphics 0x18b2cddd4 CGFontCreateFontsWithPath + 36 11 CoreGraphics 0x18b3389b0 CGFontCreateFontsWithURL + 680 12 libGSFont.dylib 0x190465518 AddFontsFromURLOrPath + 288 13 libGSFont.dylib 0x19045ffb4 RegisterURLAndCopyFaces + 168 14 libGSFont.dylib 0x19045fefc GSFontRegisterURL + 76 15 CoreText 0x181c5e0b8 _CTFontManagerRegisterActionFontsForURLs(__CFArray const*, CTFontManagerScope, bool, Action, __CFArray const**) + 396 16 IBCocoaTouchToolFoundation 0x10307e748 +[UIFont(IBCocoaTouchToolIntegration) ib_registerFontsAtURLs:] + 336 17 AssetCatalogFoundation 0x1033e1a88 __80-[IBMessageReceiveChannel deliverMessage:toTarget:withArguments:context:result:]_block_invoke + 196 18 AssetCatalogFoundation 0x1033e191c -[IBMessageReceiveChannel deliverMessage:toTarget:withArguments:context:result:] + 328 19 AssetCatalogFoundation 0x1033e14bc __88-[IBMessageReceiveChannel runBlockingReceiveLoopNotifyingQueue:notifyingTarget:context:]_block_invoke + 100 20 libdispatch.dylib 0x180178de0 _dispatch_client_callout + 16 21 libdispatch.dylib 0x180188bc8 _dispatch_async_and_wait_invoke + 112 22 libdispatch.dylib 0x180178de0 _dispatch_client_callout + 16 23 libdispatch.dylib 0x180187c60 _dispatch_main_queue_drain + 1272 24 libdispatch.dylib 0x180187758 _dispatch_main_queue_callback_4CF + 40 25 CoreFoundation 0x18041b2dc __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 26 CoreFoundation 0x180415838 __CFRunLoopRun + 1944 27 CoreFoundation 0x180414c24 CFRunLoopRunSpecific + 552 28 Foundation 0x180f319c8 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 208 29 AssetCatalogFoundation 0x1033bdc00 -[IBAbstractPlatformTool startServingReceiveChannel:] + 292 30 AssetCatalogFoundation 0x1033bddf4 -[IBAbstractPlatformTool startServingWriteDescriptor:readDescriptor:] + 96 31 AssetCatalogFoundation 0x1033be718 +[IBAbstractPlatformTool main] + 800 32 IBAgent-iOS 0x102b77930 main + 32 33 dyld_sim 0x102b89410 start_sim + 20 34 dyld 0x102c96274 start + 2840

只能在string catalog里面添加语言，不能删除语言？？这是什么设计？ 在Project里面删除语言，并不能删除Localizable中的语言。但是如果这个语言没有任何国际化，是可以的。 也就是说，删不了曾经做过国际化的语言。 我应用还没发布，还在开发呢，为什么不让我删除语言？？？？？？？？？？？？？？？？？？？？？？？？？？、

I have a Localizable file under Assets. I can add a language by click the + button. But I can't remove it then??!! Remove a localization in project -> info does not work. If the localization contains some translation, it still remains in the catalog (works if not translated at all). As a result, your app will not show the default localization at all.