Search results for

xcode github

94,046 results found

Post

Replies

Boosts

Views

Activity

Xcode Crashes While Opening or Searching Specific Files
My Xcode crashed over and over again while I searing spefic file like TingMusic. I have tried uninstall and install Xcode from 16.0 to 16.4, clear derived data folder, reboot my Mac, but none of these working. 😭 Translated Report (Full Report Below) Process: Xcode [1811] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 16.4 (23792) Build Info: IDEApplication-23792000000000000~2 (16F6) App Item ID: 497799835 App External ID: 874973124 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-09-02 10:51:26.8582 +0800 OS Version: macOS 15.6 (24G84) Report Version: 12 Anonymous UUID: 9835064A-AD7C-EE47-64DE-49587A7EC956 Time Awake Since Boot: 320 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Pro
1
0
219
2w
KeyChain Sharing with App Extensions
Hi, We are trying to use Apple Security API for KeyChain Services. The motive is to store some sensitive data in the KeyChain. Our app has Network extensions enabled which share a common app group and we want to access the data stored in the KeyChain from the extensions as well. Specifically we were exploring the SecItemAdd, SecItemCopyMatching etc family of APIs. We tried a few methods: Using the common App Group : Specifying the common app group in the kSecAttrAccessGroup field of the KeyChain query, allowed us to have a shared keychains for different apps (targets) in the app group, but this did not work for extensionsEnabling the KeyChain Sharing capability : We enabled the KeyChain Sharing Ability in the extensions and the app target as well, giving a common KeyChain Access group. Specifying this in the kSecAttrAccessGroup field also did not work.We tried specifying $AppIdentifier.KeyChainSharingGroup in the kSecAttrAccessGroup field , but this did not work as wellThe error code which we get in all these
2
0
1.4k
2w
Reply to "Signing certificate" and post-installation assignment fail due to IOPCIPrimaryMatch
Thank you for your reply. I understand that the following is a reserved character in XML: & Below are the current expected and actual values. Driverkit expected value 0x00001916&0x0000FFFF Provisioning file contents 0x00001916&0x0000FFFF Entitlements file contents 0x00001916&0x0000FFFF I'm not sure why Xcode Signing Certificate status is Failed with the above configuration. It doesn't seem to me that Driverkit and the provisioning file expect & as the expected value. Based on the above, isn't it Xcode that expects &? I'm suspicious of Xcode's behavior. I'm worried that resubmitting the authorization request won't improve the situation. Is my understanding incorrect?
Topic: Code Signing SubTopic: Entitlements Tags:
2w
WatchOS version lower than deployment target in Xcode 26
Description: I’m encountering an issue where the Apple Watch’s watchOS version is lower than the deployment target specified in my Xcode project. For example, my Watch device is running watchOS 10.6, but my app’s deployment target is set to watchOS 9.6 or 10.6, and Xcode shows an error stating: Error: “watchOS version doesn’t match the app’s deployment target.” Could someone clarify how to properly handle this version mismatch? Environment: Xcode 26 iPhone: iOS 18 Apple Watch: watchOS 10.6 Any guidance or best practices would be appreciated.
8
0
307
2w
macOS 26.1 Tahoe on ARM: FinderSync extension does not work
When running the currently latest version of macOS (26.1) on a machine with ARM CPU (I could not reproduce the issue with Intel-Based machines) Finder Sync extensions do not work any more in general. Steps to reproduce the problem: In Xcode create a new macOS App project with default settings (in my case I chose XIB for the UI and Objective-C as language, and disabled testing, but that should not make any difference) In Xcode add a new target / Finder Sync Extension to the project with default settings, this adds a new Finder Sync Extension with example code to the app. Run the application and open Finder and navigate to /Users/Shared/MySyncExtension Documents In the system settings (Login Items & Extensions) enable the extension (Listed as File Provider). On systems where it is working, in the context menu of that folder an entry Example Menu Item will appear. On systems where it does not work it is missing. Some findings: Adding the *.appex with pluginkit -a registers the extension as
10
0
287
2w
Reply to Dropping support for Intel from Mac Catalyst App
Thanks for the post. This is interesting you want to remove some support. On top of my head. What about setting the architecture the project supports? Xcode Project Settings: Open your project in Xcode. Go to your project settings by selecting the project file in the Project Navigator. Select your app target, then navigate to the Build Settings tab. In the search bar, type Valid Architectures. You may need to show all settings by clicking the All button at the top. Set Valid Architectures to arm64. This change ensures that your app is built only for Apple Silicon, which uses the ARM architecture. Will that work for what you trying to accomplish? Other developers here may have better ideas of how to drop support for Intel. Please be sure to note that if you targeting the App Store. In general, App Store does not allow you to ‘narrow’ your requirements. You can’t remove support for device type in a newer version. There is a device narrowing exception that you can apply for to allow this sort o
2w
iCloud Container Cannot Enable in Xcode — App ID Won’t Accept Container / Missing iCloud Documents Toggle
Hi everyone, I am experiencing an iCloud provisioning problem I cannot resolve, and Developer Support has not been able to help. My App ID: com.exaqservices.ArkyvTiles Symptoms: 1. In Xcode (v16.2), enabling iCloud in Signing & Capabilities repeatedly fails with: The app ID does not include the iCloud container. Click Try Again. Clicking Try Again does nothing. The error persists forever. 2. In Certificates, Identifiers & Profiles: • The iCloud capability is enabled for this App ID. • The CloudKit container is selected. • But the portal no longer shows the “iCloud Documents” checkbox, which used to be required for ubiquitous document support. 3. Xcode cannot regenerate provisioning profiles because it claims the App ID is missing the iCloud container — even though the container is attached. 4. Provisioning profiles on the Apple Developer site all appear expired, and new ones do not generate correctly. 5. The App Store Connect interface also does not show an iCloud Services section un
1
0
65
2w
Reply to WKNavigationActionPolicy of "cancel" prints stack trace to console
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Safari & Web SubTopic: General Tags:
2w
Building SimpleAudioDriver example
Hi there, I am trying to build the Apple SimpleAudioDriver example but fail with codesign and/or provisioning. I would be ok for now with the local option, but XCode 16.4 doesn't show the option build to run locally (SIP is disabled). When using Automatically manage signing it ends in a Please file a bug report. I found that having two different development teams tripped it up, so I deleted all certificates and keys and made sure to be only signed into one account in Xcode. Can anyone give advice? Thanks a ton! Here is the URL to the sample: https://developer.apple.com/documentation/coreaudio/building-an-audio-server-plug-in-and-driver-extension macOS: 15.6.1 XCode: 16.4 Hardware: MacBook Pro M2 Max SIP: disabled
11
0
1.1k
2w
Crashing build when testing my app
The Test target not build for not such file or directory: 'CoreGraphics'. Not sure why I get this error, but I configured the target without forgetting the variables BUNDLE_LOADER with $(BUILT_PRODUCTS_DIR)/MyExistingApp.app/MyExistingApp value and TEST_HOST with $(BUNDLE_LOADER) value. App target (not the test target), the Symbols Hidden by Default build setting its equal to NO, unlike the Test target that is set to YES. Any variable more for this? I'm not sure if I should take anything into account when using Xcode 26.1.1 and Swift Testing framework.
1
0
187
2w
Signing & Capabilities related issue
I am using Automatically Manage Signing And I have registered my Mac UUID in developer account, but it is still giving me these errors - Device My Mac is not registered to your team Ai Glider Inc. Devices must be registered in order to run your code, but you do not have permission to register them. Please check with your team's admin. No profiles for 'com.aiexample.sebexample' were found Xcode couldn't find any Mac App Development provisioning profiles matching 'com.aiexample.sebexample'.
5
0
399
2w
Reply to Show device's provisioning profiles
[quote='867739022, chrismuench, /thread/769472?answerId=867739022#867739022, /profile/chrismuench'] I still have this problem with Xcode 26! [/quote] That gels with my reading of this bug’s state (FB7791261). [quote='867739022, chrismuench, /thread/769472?answerId=867739022#867739022, /profile/chrismuench'] I still have this problem with Xcode 26! Is there any solution for this? [/quote] Solution to what? This bug prevents you from seeing the device’s profiles, but that doesn’t prevent you from developing. In the standard development workflow your app’s provisioning profile is embedded in the app itself, so this view is irrelevant. If the app is installed, it’s profile is installed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w