Search results for

xcode github

94,736 results found

Post

Replies

Boosts

Views

Activity

StoreKit Config file Options Grayed Out
I have a question concerning Xcode version 26. Ever since I installed this version on my Mac, I have been experiencing issues with the StoreKit configuration file. The Simulated StoreKit Failures check boxes and selections are all grayed out. Once in a while, I see a pop-up stating The document 'TaConfig.storekit' could not be autosaved. The file has been changed by another application. The pop-up Save as... points to where my config file is located, but the config file is grayed out. I thought maybe the directory where the file is located is write protected, but I have been able to save other files to the same directory. The Edit Scheme... -> Run -> Options has the StoreKit Configuration set for my file TaConfig.storekit. It feels like there is an option somewhere that I'm missing.
Topic: Developer Tools & Services SubTopic: Xcode
2
0
265
4w
Reply to UI Tests troubles with Xcode 26.1 and Xcode 26.2
So, after more tests and refactoring, we have the feeling all this mess started from our custom component providing a TabView with more or less customization depending to the OS version (i.e. Liquid Glass or not). Our old implementation, with a ZStack and some conditions inside, brought this cycle in attributes graph issue. Such cycle broke the view hierarchy, the UI tests and had side effects on other elements of navigation. The only interesting thing I can share is our Git diff (on GitHub, public repository,hope it would help someone.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
4w
UI Tests troubles with Xcode 26.1 and Xcode 26.2
Since I moved to Xcode 26.1 and Xcode 26.2 then, my UI tests all fail only for iOS 26+, for both simulator and real device. Everything worked perfectly with Xcode 26.0, and the code base of the application under test and the test cases are the same. With Xcode 26.0, the tests pass for iOS 26+ and iOS < 26, for both simulator and real device. In addition, even the Accessibility Inspector tool fails to display the view hierarchy for iOS 26+ with Xcode 26.2. With Xcode 26.0, whatever are the devices and the OS versions, the tool was able to display the view hierarchy. Otherwise the tool is empty even if the device and app are selected. This failing tests issue occurs both on my local environment and on GitHub Actions runners, excluding the hypothesis I have troubles with my own side. The error message for failing tests explains the element cannot be found anymore. Given for example the test case: @MainActor func testMakeScreenshotsForDocumentation
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2
0
258
4w
Reply to SensorKit - Questions about the startRecording() and data holding period
If the user toggled the permission (turned off and turned on again) in Settings Privacy & Security -> Research Sensor & Usage Data -> Optical Sensor -> apps and studies with access, will the holding period get reset ? The 24 hours holding period is counting from the calendar day 24:00 or the time startRecording() got called ? I tried the following step but got a empty export, any ideas why ? Delete the app Install the app from Xcode with dev profile Called startRecording() and wait 24 hours exactly During the 24 hours, I wore my watch for around 12 hours, and update the app in place(without change the Xcode build number) for couple times. Export from system settings Optical Sensor -> Export All Current Collected Data
Topic: App & System Services SubTopic: General Tags:
4w
Metal debug log in Swift Package
My goal is to print a debug message from a shader. I follow the guide that orders to set -fmetal-enable-logging metal compiler flag and following environment variables: MTL_LOG_LEVEL=MTLLogLevelDebug MTL_LOG_BUFFER_SIZE=2048 MTL_LOG_TO_STDERR=1 However there's an issue with the guide, it's only covers Xcode project setup, however I'm working on a Swift Package. It has a Metal-only target that's included into main target like this: targets: [ // A separate target for shaders. .target( name: MetalShaders, resources: [ .process(Metal) ], plugins: [ // https://github.com/schwa/MetalCompilerPlugin .plugin(name: MetalCompilerPlugin, package: MetalCompilerPlugin) ] ), // Main target .target( name: MegApp, dependencies: [MetalShaders] ), .testTarget( name: MegAppTests, dependencies: [ MegApp, MetalShaders, ] ] So to apply compiler flag I use MetalCompilerPlugin which emits debug.metallib, it also allows to define DEBUG macro for shaders. This code compiles: #ifdef DEBUG logger.log_error(Hello There!); os_log
Topic: Graphics & Games SubTopic: Metal Tags:
1
0
578
4w
Reply to XCode26 - Unable to launch Image in storyboard for landscape picture in Portrait orientation
I had updated the github code here for the setting . Please advise the specific setting The configuration that I see in the GitHub repository looks correct now in terms of overall configuration of your Launch Storyboard and the overall keys. However, I will reiterate what I said earlier to make sure that the contents of your launch screen match the Human Interface Guidelines. — Ed Ford,  DTS Engineer
Topic: UI Frameworks SubTopic: SwiftUI Tags:
4w
Xcode Interface Localization
I understand that mastering essential English skills is fundamental for developers. However, as a Chinese developer, having an IDE with a Chinese interface when encountering Xcode operational issues can absolutely make development work twice as effective with half the effort. A native-language interface environment allows us to focus all our energy on project development. Xcode exists as our development “tool” to facilitate our work, not as another knowledge point requiring study—which could waste significant effort. Don't let an interface turn our beloved tool into a burden. Translated with DeepL.com (free version)
Topic: Developer Tools & Services SubTopic: Xcode
1
0
179
4w
Reply to How can I configure the application or environment to suppress this repeated permission prompt?"
Hi @Ankita-Shrivastava, These forums for intended for code-level questions from our Developer community. This question is about a user-facing feature of macOS. Please see the following support page for more details about Full Disk Access: Mac User Guide: Change Privacy & Security settings on Mac https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/15.0/mac/15.0#:~:text=Full%20Disk%20Access Cheers, Paris X Pinkney |  WWDR | DTS Engineer
Topic: Privacy & Security SubTopic: General
4w
Reply to Multi-machine Code Signing
Thanks for the replies. You are both quite right that I should have provided more information. When I say that notarization succeeds, I mean that I submit the dmg file produced by the build to the Apple notarization service and receive a status of 'Accepted'. I take this to mean all is well. When I say that notarization fails, I mean that the notarization step produces a status of 'Invalid'. Retrieving the notarization log indicates that the binaries were not signed. I've just gone through this again with my two machines. The build here is performed by scripts that are maintained in source code control and forced to be identical in both setups. The build infrastructure is also the same for both. Before beginning, both machines were powered off for a period of time. Power up one machine. Ensure the source tree is up-to-date. Run the build to produce a signed dmg. Submit it for notarization. The submission produces a status of Accepted. Power down the first machine. Power up the second machine. Again ensure the
Topic: Code Signing SubTopic: Notarization
4w
DYLD_PRINT_STATISTICS
Did DYLD_PRINT_STATISTICS stop working? I am using Xcode 26.0.1 and have tried it on several simulators and real devices, but am not getting any output. I haven't used this environment variable in a few years so don't know when it might have stopped working. Has it been superseded or replaced?
Topic: Developer Tools & Services SubTopic: Xcode
2
0
241
4w
Unable to profile Metal app on M2 Ultra (profiling works on M3 Pro)
On MacBook Pro M3 14 I can profile the Metal App performance by running it, then clicking on the M icon and choosing profile after replay. On Mac Studio M2 Ultra I cannot: the profiler starts and crashes. I have tried everything including reinstalling the OS, Xcode, the Metal SDK, you name it. The app uses the Metal 4 API. The content of the replayer errorinfo report is shown at the end. Any ideas what is going on here and/or what else I can do do root cause this and fix it? FWIW, it was worse on 26.1 (Xcode just reported Metal 4 profiling not available). In 26.2 Xcode attempts to profile and invariably crashes. === Error summary: === 1x DYErrorDomain (512) - guest app crashed (512) 1x com.apple.gputools.MTLReplayer (100) - Abort trap: 6 === First Error === Domain: DYErrorDomain Error code: 512 Description: guest app crashed (512) GTErrorKeyPID: 26913 GTErrorKeyProcessName: GPUToolsReplayService GTErrorKeyCrashDate: 2026-01-09 19:22:52 +0000 === Underlying Error #1 === Domain: com.a
Topic: Graphics & Games SubTopic: Metal
1
0
350
4w
Code Coverage Not Accurate in Xcode 26
Description: I’m noticing that the code coverage metrics in Xcode 26 are not accurate compared to earlier versions. In Xcode 15, the same set of unit tests shows around 38% coverage, but in Xcode 26, even though all the tests are running successfully (for example, the SegmentedUI test cases), the code coverage is displayed as 0%. Has anyone else observed this behavior in Xcode 26? Is there any known issue, workaround, or configuration change required to get the correct coverage report? Environment: Xcode 26 iOS 18 SDK Unit tests running under XCTest Any insights or suggestions would be appreciated.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
419
4w