Search results for

xcode github

93,978 results found

Post

Replies

Boosts

Views

Activity

Reply to Need Inputs on Which Extension to Use
Hi @DTS Engineer , Thanks a lot for your clarifications again!! I’m working with the NETransparentProxyProvider class for a network extension app in my macOS. However, I’ve encountered an issue where the Transparent Proxy extension does not activate when the system is offline (network disabled). Here are the details: Content Filter extension is active and functioning properly(offline as well) Both the Transparent Proxy and Content Filter extensions are under the same Xcode target. I can see the Transparent Proxy extension listed in Settings → Network → Filters & Proxies, but it shows as Disabled.(offline) My question: Is an active network connection required for the NETransparentProxyProvider extension to be enabled/activated, even temporarily, during installation? Background: The environment where I’m installing the system extension doesn’t have network access (e.g., in sandboxed VMs). Once installed, the extensions are always running, but the main app process (Xcode target 1) is starte
Topic: App & System Services SubTopic: Networking Tags:
1h
Reply to In Simulator on status bar red banner with rdar:45025538
Here’s what’s going on and how I fixed it locally. Once you install and run a newer Xcode (for example 26.2), it performs a CoreSimulator migration and writes system-wide frameworks into /Library/Developer/PrivateFrameworks. This migration is global and there’s no rollback mechanism. Even if you delete Xcode 26.2 and keep using Xcode 26.1.1, the older Simulator binary still loads CoreSimulator frameworks from the system location, not from inside the Xcode bundle. So you end up in a situation where Simulator.app is launched from /Applications/Xcode-26.1.1.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator but it’s actually using newer system frameworks like: /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator /CoreSimDeviceIO.framework /SimPasteboardPlus.framework /CoreSimulatorUtilities.framework In my case the CoreSimulator version there was already 1051.17.7, which clearly came from Xcode 26.2. Th
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2h
Gitlab CI: Unable to find a device matching the provided destination specifier
Gitlab runner on M4 Mac Mini 2024, XCode 26.2, supported platforms: iOS, native UIKit swift project. Cocoapods. Trying to run tests via fastlane: run_tests(workspace: 'Project.xcworkspace', destination: platform=macOS,id=#{deviceId}, scheme: Release, clean: true) And having an error: $ xcodebuild -showBuildSettings -workspace Project.xcworkspace -scheme Release -destination platform=macOS,id=01234567-0123456789B9001C 2>&1 [12:23:53]: Could not read the SUPPORTED_PLATFORMS build setting, assuming that the project supports iOS only. [12:23:54]: Found simulator iPhone 16 Pro (18.5) The tests runs just fine in xcode on My Mac (Designed for iPad) device on the very same machine. Compared the output of xcodebuild -showdestinations in terminal: $ xcodebuild -showdestinations -workspace Project.xcworkspace -scheme Release Available destinations for the Release scheme: { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:01234567-0123456789B9001C, name:My Mac } { platform:iOS,
Topic: Developer Tools & Services SubTopic: Xcode
0
0
18
5h
Xcode Cloud: Preparing build for App Store Connect failed
Error: Preparing build for App Store Connect failed No error logs in log view. Download the archive and try to submit to App Store: Detailed logs: 2025-12-17 07:26:00 +0000 [MT] Command line name app-store is deprecated. Use app-store-connect instead. 2025-12-17 07:26:00 +0000 App Store Connect request for store configuration failed for account Session Proxy Provider (Account Session Proxy Provider: Unable to authenticate with App Store Connect (Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 (null))) 2025-12-17 07:26:00 +0000 App Store Connect response failed with unknown failure for credential ; response (null); error (null). 2025-12-17 07:26:00 +0000 App Store Connect request for store configuration for credential ; configuration: (null); error DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy 2025-12-17 07:26:00 +0000 [MT] Failed to find an account with App Store Connect
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
0
0
26
5h
Reply to Xcode 26.1 re-release?
There was a release of Xcode 26.2 that was dated December 4th. Then there was a release of Xcode 26.1 on December 16. Which is the most current? Why was there a later release of 26.1 when there was a ralease of that level in November 11 followed by a 26.1.1? This release strategy is somewhat confusing.
Topic: Developer Tools & Services SubTopic: Xcode
9h
Reply to Xcode Cloud Export Archive Fails with Xcode 26.2 RC
@Gong Thank you for providing the comprehensive post and the bug report number. You made sure to use the release version of Xcode correct? 17C52? Please allow the engineering team ample time to investigate this issue, considering the upcoming holiday season. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
12h
Reply to App Review Rejected, Invalid Binary, App Version
Thanks for the post. Have you search the forums for this issue? Are you utilizing any other software besides Xcode? Are you using Objective-C with empty names in the metadata? To identify the binaries with those conditions, you can run the following Terminal command on each binary inside the app: ‘% xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null)”’ Can you check the build log in Xcode and provide me with those messages including the warnings are really important and may give us a clue. Can you share those warnings? Additionally, could you please share the Xcode version, the minimum operating system requirements, and any relevant build settings that may be pertinent to this task? I eagerly anticipate your responses to guide you toward a comprehensive resolution for this matter, provided the script yields favorable outcomes. Otherwise if is not the issue I am thinking with Objective-C, please get it touch with App Store Connect support as they’ll have the reason the bi
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
12h
Reply to Instruments Crash using swiftui instrument
Thanks for the post. It looks like you're encountering a specific crash related to the SwiftUI instrument in Xcode 26.2, which can be quite frustrating, especially when it interrupts a useful workflow. Given that you've already attempted some common troubleshooting steps like removing derived data, reinstalling, updating Xcode, and restarting devices, and that is a crash on the Instruments app let’s go ahead and file a bug: Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Instruments Tags:
12h
Instruments Crash using swiftui instrument
Instruments is crashing when the swiftui instrument is stopped (the session is finished) and the transfer begins from device to device: Crashed Thread: 11 Dispatch queue: com.apple.swiftuitracingsupport.reading Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1633] I've tried removing derived data, reinstalling xcode, updating xcode (I originally thought this might be the issue -- I needed to update to 26.2 from the 26 RC -- the update didn't fix crash or change the crash report), and restarting both devices. I'm running Instruments/Xcode 26.2 on a MacBook Pro 15 (2018) running Mac OS 15.7.2 (24G325) with an iPhone 16 Pro Max running 26.2. Hoping someone else might have seen this or could help me troubleshoot. I find the swiftui instrument be helpful and like to use it :) I can post a complete crash report as well.
Topic: Developer Tools & Services SubTopic: Instruments Tags:
1
0
18
12h
Reply to XCTFail immediately aborts the test in Xcode 26 — no retry on failure
This is a known issue in Xcode 26 and later. When using XCTest in Xcode 26 and later, a test failure will cause the test runner process to terminate and relaunch before continuing to the next test if all the following conditions are met: The test class is written in Swift, The test’s continueAfterFailure property is set to false, Either the test method is async or the async overload of setUp or tearDown is overridden, and The test encounters a failure. Under these conditions, the first issue recorded by each affected test will cause the test runner process to be terminated after its tearDown sequence finishes. A new test runner process will then be launched, and execution will continue with the next test. This applies to any XCTAssert calls which fail, all calls to XCTFail, and failures encountered by UI automation API calls. This change was made to XCTest in order to improve reliability, since the XCTestCase.continueAfterFailure API uses Objective-C exceptions and can cause problems when us
Topic: Developer Tools & Services SubTopic: Xcode Tags:
13h
Reply to UIImageWriteToSavedPhotosAlbum doesn't working on Mac catalyst
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: Programming Languages SubTopic: Swift Tags:
14h
Xcode 26.1 re-release?
The developer downloads page now lists an Xcode 26.1 which was released on 11th Dec (the original Xcode 26.1 was posted on 3rd Nov). Strangely, this new Xcode 26.1 has a CFBundleShortVersionString of 26.1.1, and a DTXcodeBuild of 17B55 % ls -ln total 4413136 -rw-r--r--@ 1 503 20 2259523057 16 Dec 19:01 Xcode_26.1_Apple_silicon.xip % xip --expand Xcode_26.1_Apple_silicon.xip xip: signing certificate was Software Update (validation not attempted) xip: expanded items from /Users/me/Downloads/temp/Xcode_26.1_Apple_silicon.xip % plutil -p Xcode.app/Contents/Info.plist | grep CFBundleShort CFBundleShortVersionString => 26.1.1 % plutil -p Xcode.app/Contents/Info.plist | grep DTXcodeBuild DTXcodeBuild => 17B55 17B55 does correspond to the original Xcode 26.1 final release. The Xcode 26.1.1 release that was previously posted had a DTXcodeBuild of 17B100, though. The pairing of 26.1.1 and 17B55 looks new and probably a packaging error?
Topic: Developer Tools & Services SubTopic: Xcode
2
0
101
17h
Reply to [Texas SB 2420] How to Retrieve Parental Consent Status
Hi @Umeki, To enable all the technologies and access all the signals Apple has made available to comply with regional age assurance requirements, starting with Texas, you must build your app against the iOS 26.2 and iPadOS 26.2 SDKs and later, with Xcode 26.2 (17C52) and later. To view the latest Xcode versions and SDKs, see here. As of iOS 26.2 and iPadOS 26.2, age assurance includes the following signals: Declared Age Range API — Determine whether a person using your app is in an applicable region that requires additional age-related obligations. When a child account, or their parent or guardian, chooses to share age information, the Declared Age Range API will return the age band or age category, depending on legal requirements in the region. The API will also provide information about the method used to confirm the age band or category, whether parental controls are enabled, and whether the user is eligible for age gated features. For more details, see the following documentation: AgeRan
Topic: App & System Services SubTopic: General Tags:
17h