Search results for

“xcode github”

95,388 results found

Post

Replies

Boosts

Views

Activity

Reply to PencilKit PKCanvasView flicker
Thank you for the sample project and the video — both were very helpful. We were able to reproduce the flickering on iPad with Apple Pencil using your sample project. We tested several potential app-level workarounds (deferring contentInset updates, guarding against layout recalculation during active drawing, consolidating CATransaction blocks) but none of them resolved the issue. Based on our investigation, the flicker appears to be occurring within PKCanvasView's internal tile rendering when drawing at non-1x zoom scales, rather than being caused by anything in your app code. 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. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to
2d
Simulator was shutdown during an update
I am trying to preview my SwiftUI views but Xcode Preview Canvas failing. I tried everything that I found at internet but nothing works. Finally I created a new iOS project that contains only a view import SwiftUI struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Text(Hello, world!) } .padding() } } #Preview { ContentView() } Even this view cannot be previewed The error is Simulator was shutdown during an update Simulator [3E0DB935-C4C2-4566-BA48-8E21564C207C] failed to boot and may have crashed. I tried to restart xCode, restart Mac, download ios 26.0 sdk and created a simulator with that sdk but nothing helped. Do you have an idea?
1
0
55
2d
Reply to Simulator was shutdown during an update
Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appe
2d
Reply to Icon composer icon contains alpha channel upload error
Following the documentation here also did not work for me. https://developer.apple.com/documentation/xcode/creating-your-app-icon-using-icon-composer#Add-your-Icon-Composer-file-to-an-Xcode-project What worked for me was the following: In Icon Composer, select File -> Export... For Appearance, select All, then click Export... Select a location and click Export to save Navigate to the location you saved, there should be 6 .png files. Select the three you will use for AppIcon from assets for Any Appearance, Dark, and Tinted options. Open those in Preview In Preview for each image, select File -> Export... Be sure to uncheck the Alpha setting and save the file. Use the newly exported images for your three AppIcon settings in Assets.
2d
spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
I'm distributing a macOS .pkg installer signed with Developer ID Installer and notarized via notarytool. On macOS 26.3 (Tahoe, Build 25D125), the package is rejected by Gatekeeper when downloaded from the internet. What works: pkgutil --check-signature → signed, Developer ID Installer, full chain (G2 intermediate + Apple Root CA) xcrun stapler validate → The validate action worked! xcrun notarytool info → status: Accepted The .app inside the .pkg passes spctl -a -vvv → accepted, source=Notarized Developer ID What fails: spctl -a -vvv --type install mypackage.pkg → rejected, origin=Developer ID Installer Raw assessment: assessment:remote = true, assessment:verdict = false Double-clicking the downloaded .pkg shows only Move to Trash / Done (no Open option) syspolicyd log: meetsDeveloperIDLegacyAllowedPolicy = 0 (expected, since the cert is new), but no notarized match is logged Certificate details: Developer ID Installer, issued Feb 28, 2026, valid until 2031 OID 1.2.840.113635.100.6.1.14 (Developer ID Install
4
0
652
2d
AlarmKit sometimes creates a blank (empty) Live Activity
Hi! My users have reported (and I have observed) a blank Live Activity where only a black capsule is shown in the dynamic island. When tapping that capsule, the app opens, but inside the capsule, nothing is shown. The Live Activity is created through the AlarmKit API like this: let identifier = UUID() Task { do { _ = try await AlarmManager.shared.schedule( id: identifier, configuration: .init( countdownDuration: countdownDuration, attributes: attributes, stopIntent: CancelTimerIntent(), secondaryIntent: RestartTimerIntent(), sound: Settings.shared.systemAlarmToneEnabled ? .default : .named(Settings.shared.alarmTone[.loop].filename) ) ) Log.debug(Alarm scheduled successfully: (identifier.uuidString)) } catch { Log.error(Error scheduling alarm with id (identifier.uuidString), error: (error)) } } I've read some other forum posts where developers reported the same issue: https://developer.apple.com/forums/thread/807335 https://developer.apple.com/forums/thread/812006 I assume, it has something to do with state ma
1
0
83
2d
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
AFAIK there’s no magic here. And I tried reproducing this on my main work Mac and didn’t have a problem. Specifically: On macOS 26.3.1, I downloaded the current 26.4rc seed (UniversalMac_26.4_25E243_Restore.ipsw). Using an off-the-shelf Virtualization framework app [1], I created a VM from that. It installed and booted, and I was able to run all the way through MacBuddy and get to the Finder. I’m not sure why this is failing in your environment. This Mac is production hardware that’s only ever run released system software (plus various Xcode beta seeds). When I wrote the above I hadn’t yet installed Xcode 26.4rc. So I installed that and repeated the test. It didn’t change anything. Things continued to work. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] VirtualBuddy 2.1.
Topic: App & System Services SubTopic: Core OS Tags:
2d
Reply to Does signed macho binary with teamID is signed by Apple root certificate
[quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] I need to support both use case (exec and dylib). [/quote] OK. [quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] [Library validation] does not apply in my scenario since the library is provided by a third party [/quote] I’d like to better understand that. It’s quite common for Mac apps to use libraries created by other developers, and they retain library validation by re-signing those libraries. Is there something preventing you from doing that in this case? The most obvious case where folks need to disable library validation is that their app supports in-process plug-ins, where those plug-ins are built and shipped by other third-party developers in a way that’s completely independent of the main app’s vendor. Is that what’s happening here? Because if you’re managing these plug-in releases then it’d be better to have you re-sign the plug-in and leave library validation enab
2d
hapticpatternlibrary.plist error with Text entry fields in Simulator only
When I have a TextField or TextEditor, tapping into it produces these two console entries about 18 times each: CHHapticPattern.mm:487 +[CHHapticPattern patternForKey:error:]: Failed to read pattern library data: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000ca1b30 {Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory}} <_UIKBFeedbackGenerator: 0x600003505290>: Error creating CHHapticPattern: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnd
4
0
653
2d
ScreenCaptureKit permissions lost after every build — solved by switching signing identity
Sharing a solution for a problem that took me a while to figure out. Problem: During development of a macOS 26 app that uses ScreenCaptureKit, the screen capture permissions were being reset after every build. Each time I compiled and ran the app from Xcode, I had to re-authorize screen capture in System Settings. CGPreflightScreenCaptureAccess() would return false even though I'd just granted permission minutes ago. Root cause: I was using ad-hoc code signing during development. macOS ties screen capture permissions to the app's code signing identity. With ad-hoc signing, the identity changes on every build, so the system treats each build as a new app. Solution: Switch to an Apple Development certificate for debug builds. In Xcode: Build Settings → Code Signing Identity → Debug → set to Apple Development Make sure your development team is selected After this change, the signing identity remains stable across builds, and screen capture permissions persist. This might be related to the broad
1
0
401
2d
Reply to PencilKit PKCanvasView flicker
Thank you for the sample project and the video — both were very helpful. We were able to reproduce the flickering on iPad with Apple Pencil using your sample project. We tested several potential app-level workarounds (deferring contentInset updates, guarding against layout recalculation during active drawing, consolidating CATransaction blocks) but none of them resolved the issue. Based on our investigation, the flicker appears to be occurring within PKCanvasView's internal tile rendering when drawing at non-1x zoom scales, rather than being caused by anything in your app code. 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. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to
Replies
Boosts
Views
Activity
2d
Reply to sandbox purchase completes but app review gets stuck
There are a lot of topics about 'RevenueCat.' I would take a look at all of them if I were you. Actually, I think, I have read a quite similar topic probably a week ago. I do everything with Xcode. So I cannot offer a clue of any kind. I don't even know why people use RevenueCat. I only know the name. I would also find out if RevenueCat has support forums.
Replies
Boosts
Views
Activity
2d
Reply to All Xcode projects showing up in source control navigator.
Git repos can be big source of this problem. But there's one more to check. Xcode projects actually consist of two parts - the project and the workspace. The source code integrations are based on the workspace. Xcode uses a shared workspace by default. But you can create a dedicated workspace file for your project and then just open that file instead of the project file.
Replies
Boosts
Views
Activity
2d
All Xcode projects showing up in source control navigator.
This just started happening today out of nowhere. Instead of only the project I’m working on appearing in Source Control, every project inside my Xcode projects folder is now showing up in the Source Control navigator. This is happening in both the Changes and Repositories tabs.
Replies
2
Boosts
0
Views
155
Activity
1d
Reply to All Xcode projects showing up in source control navigator.
Hi! Could you check whether you've created a git repo in a parent folder relative to your projects? For example, in your home folder. When a project is opened in Xcode, it searches all parent folders for a git repo, so that it is able to correlate workspaces that span multiple projects, and this could be triggering that logic.
Replies
Boosts
Views
Activity
2d
Simulator was shutdown during an update
I am trying to preview my SwiftUI views but Xcode Preview Canvas failing. I tried everything that I found at internet but nothing works. Finally I created a new iOS project that contains only a view import SwiftUI struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Text(Hello, world!) } .padding() } } #Preview { ContentView() } Even this view cannot be previewed The error is Simulator was shutdown during an update Simulator [3E0DB935-C4C2-4566-BA48-8E21564C207C] failed to boot and may have crashed. I tried to restart xCode, restart Mac, download ios 26.0 sdk and created a simulator with that sdk but nothing helped. Do you have an idea?
Replies
1
Boosts
0
Views
55
Activity
2d
Reply to Simulator was shutdown during an update
Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appe
Replies
Boosts
Views
Activity
2d
Reply to Icon composer icon contains alpha channel upload error
Following the documentation here also did not work for me. https://developer.apple.com/documentation/xcode/creating-your-app-icon-using-icon-composer#Add-your-Icon-Composer-file-to-an-Xcode-project What worked for me was the following: In Icon Composer, select File -> Export... For Appearance, select All, then click Export... Select a location and click Export to save Navigate to the location you saved, there should be 6 .png files. Select the three you will use for AppIcon from assets for Any Appearance, Dark, and Tinted options. Open those in Preview In Preview for each image, select File -> Export... Be sure to uncheck the Alpha setting and save the file. Use the newly exported images for your three AppIcon settings in Assets.
Replies
Boosts
Views
Activity
2d
Icon composer icon contains alpha channel upload error
When creating an icon using icon composer, I cant upload a build to testflight/App Store connect. Running on device from Xcode works fine, but as soon as I archive and upload to App Store Connect, I get an error saying the icon contains an alpha channel
Replies
40
Boosts
0
Views
2.7k
Activity
2d
spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
I'm distributing a macOS .pkg installer signed with Developer ID Installer and notarized via notarytool. On macOS 26.3 (Tahoe, Build 25D125), the package is rejected by Gatekeeper when downloaded from the internet. What works: pkgutil --check-signature → signed, Developer ID Installer, full chain (G2 intermediate + Apple Root CA) xcrun stapler validate → The validate action worked! xcrun notarytool info → status: Accepted The .app inside the .pkg passes spctl -a -vvv → accepted, source=Notarized Developer ID What fails: spctl -a -vvv --type install mypackage.pkg → rejected, origin=Developer ID Installer Raw assessment: assessment:remote = true, assessment:verdict = false Double-clicking the downloaded .pkg shows only Move to Trash / Done (no Open option) syspolicyd log: meetsDeveloperIDLegacyAllowedPolicy = 0 (expected, since the cert is new), but no notarized match is logged Certificate details: Developer ID Installer, issued Feb 28, 2026, valid until 2031 OID 1.2.840.113635.100.6.1.14 (Developer ID Install
Replies
4
Boosts
0
Views
652
Activity
2d
AlarmKit sometimes creates a blank (empty) Live Activity
Hi! My users have reported (and I have observed) a blank Live Activity where only a black capsule is shown in the dynamic island. When tapping that capsule, the app opens, but inside the capsule, nothing is shown. The Live Activity is created through the AlarmKit API like this: let identifier = UUID() Task { do { _ = try await AlarmManager.shared.schedule( id: identifier, configuration: .init( countdownDuration: countdownDuration, attributes: attributes, stopIntent: CancelTimerIntent(), secondaryIntent: RestartTimerIntent(), sound: Settings.shared.systemAlarmToneEnabled ? .default : .named(Settings.shared.alarmTone[.loop].filename) ) ) Log.debug(Alarm scheduled successfully: (identifier.uuidString)) } catch { Log.error(Error scheduling alarm with id (identifier.uuidString), error: (error)) } } I've read some other forum posts where developers reported the same issue: https://developer.apple.com/forums/thread/807335 https://developer.apple.com/forums/thread/812006 I assume, it has something to do with state ma
Replies
1
Boosts
0
Views
83
Activity
2d
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
AFAIK there’s no magic here. And I tried reproducing this on my main work Mac and didn’t have a problem. Specifically: On macOS 26.3.1, I downloaded the current 26.4rc seed (UniversalMac_26.4_25E243_Restore.ipsw). Using an off-the-shelf Virtualization framework app [1], I created a VM from that. It installed and booted, and I was able to run all the way through MacBuddy and get to the Finder. I’m not sure why this is failing in your environment. This Mac is production hardware that’s only ever run released system software (plus various Xcode beta seeds). When I wrote the above I hadn’t yet installed Xcode 26.4rc. So I installed that and repeated the test. It didn’t change anything. Things continued to work. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] VirtualBuddy 2.1.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
2d
Reply to Does signed macho binary with teamID is signed by Apple root certificate
[quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] I need to support both use case (exec and dylib). [/quote] OK. [quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] [Library validation] does not apply in my scenario since the library is provided by a third party [/quote] I’d like to better understand that. It’s quite common for Mac apps to use libraries created by other developers, and they retain library validation by re-signing those libraries. Is there something preventing you from doing that in this case? The most obvious case where folks need to disable library validation is that their app supports in-process plug-ins, where those plug-ins are built and shipped by other third-party developers in a way that’s completely independent of the main app’s vendor. Is that what’s happening here? Because if you’re managing these plug-in releases then it’d be better to have you re-sign the plug-in and leave library validation enab
Replies
Boosts
Views
Activity
2d
hapticpatternlibrary.plist error with Text entry fields in Simulator only
When I have a TextField or TextEditor, tapping into it produces these two console entries about 18 times each: CHHapticPattern.mm:487 +[CHHapticPattern patternForKey:error:]: Failed to read pattern library data: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000ca1b30 {Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory}} <_UIKBFeedbackGenerator: 0x600003505290>: Error creating CHHapticPattern: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnd
Replies
4
Boosts
0
Views
653
Activity
2d
ScreenCaptureKit permissions lost after every build — solved by switching signing identity
Sharing a solution for a problem that took me a while to figure out. Problem: During development of a macOS 26 app that uses ScreenCaptureKit, the screen capture permissions were being reset after every build. Each time I compiled and ran the app from Xcode, I had to re-authorize screen capture in System Settings. CGPreflightScreenCaptureAccess() would return false even though I'd just granted permission minutes ago. Root cause: I was using ad-hoc code signing during development. macOS ties screen capture permissions to the app's code signing identity. With ad-hoc signing, the identity changes on every build, so the system treats each build as a new app. Solution: Switch to an Apple Development certificate for debug builds. In Xcode: Build Settings → Code Signing Identity → Debug → set to Apple Development Make sure your development team is selected After this change, the signing identity remains stable across builds, and screen capture permissions persist. This might be related to the broad
Replies
1
Boosts
0
Views
401
Activity
2d