Search results for

“xcode github”

95,434 results found

Post

Replies

Boosts

Views

Activity

Xcode 9 GM Very sluggish
Just got the latest Xcode 9 (GM), and is it me or is it extremely sluggish compared to the old Xcode 8.x?Typing code seems to stagger, running the apps on the simulator seems to take a long time to start. Even the simulator is very unresponsive as well (bug reported to apple) and also screen drawing seems to messed up from time to time (for the simulator that is).I have disabled the 'source control' setting, but no effect. It is still very sluggish. Any one else experiencing this?
2
0
520
Sep ’17
Are Xcode warnings like this safe to submit (won’t disqualify)?
I’m building a Swift Playgrounds app (.swiftpm) in Xcode 26.2 and I consistently see this warning, even on brand-new Swift Playgrounds apps created from the default template: “Skipping duplicate build file in Compile Sources build phase: /Users/.../.swiftpm/Media.xcassets” Everything builds and runs normally and all images/assets appear correctly, so it seems like it’s just an annoying warning. I’ve checked for duplicates and don’t see the asset catalog listed twice, but the warning still appears whenever I add an asset catalog to any playground project in Xcode. Is this warning safe to ignore for submission, and it won’t affect Swift Student Challenge eligibility?
5
0
312
3w
Title: Developer ID + DNS Proxy system extension: profile mismatch for `com.apple.developer.networking.networkextension`
I’m building a macOS app with a DNS Proxy system extension for Developer ID + notarization, deployed via MDM, and Xcode fails the Developer ID Release build with a provisioning profile mismatch for com.apple.developer.networking.networkextension. Environment macOS: Sequoia (15.7.2) Xcode: 26.2 Distribution: Developer ID + notarization, deployed via MDM Host bundle ID: com.mydns.agent.MyDNSMacProxy DNS Proxy system extension bundle ID: com.mydns.agent.MyDNSMacProxy.dnsProxy Host entitlements (Release): File: MyDNSMacProxy/MyDNSMacProxyRelease.entitlements: http://www.apple.com/DTDs/PropertyList-1.0.dtd> com.apple.application-identifier B234657989.com.mydns.agent.MyDNSMacProxy com.apple.developer.networking.networkextension dns-proxy com.apple.developer.system-extension.install com.apple.developer.team-identifier B234657989 com.apple.security.app-sandbox com.apple.security.application-groups group.com.mydns.MyDNSmac keychain-access-groups B234657989.* xcodebuild -showBuildSettin
4
0
188
3w
Reply to Question about personal account switching to organization
The term personal account is confusing, so let me start by clarify that. The developer programme has three tiers [1]: Any Apple Account can be used for basic development. Xcode shows this as a Personal Team. This comes with significant limitations. For the details, see Developer > Support > Choosing a Membership. You can pay to join the developer programme, which makes for an Individual team. A company can pay to join the developer programme, which makes for an Organization team. You can learn more about these in Developer > Program and related pages. If you join the Individual programme you can upgrade your team to an Organization team later on. See Developer Account Helper > Membership > Updating your account information > Updating an individual membership to an organization membership. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There’s also the enterprise programme, but that’s not relevant to this threa
3w
Xcode Cloud Build times out in notarization step
We have been using Xcode Cloud Build to test an internal app. A new build is triggered automatically by a merge to main in github. Up until a few weeks ago everything was fine, we would get a notarize button and a download link. On 1/29/2026 the process started timing out at the finalizing step. The logs in the UI show no errors just a cancelled flag after 8-12 hours. Clicking the logs tab shows all green up until the step you would normally expect a stapling. Any thoughts on were to look to triage this?
1
0
222
3w
Reply to Can my submission be ran on iPhone?
Right. The submission form has two options: Swift Playground 4.6 or later Xcode 26 or later (with a note saying “Xcode app playgrounds are run in Simulator.”) In the first case, your submission must necessarily be run on an iPad. In the second, your submission will be run on the simulator, not a real device. There are some caveats here: In the first case, the Swift Playground app doesn’t yet include support for the iOS 26 SDK )-: See this thread. In the second case, the form doesn’t currently say whether it’ll be an iPhone on iPad simulator. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
3w
nonisolated Execution Differences Before and After Xcode 26.2
I have an older project that was created before Xcode 26.2. In Xcode versions prior to 26.2, there was no Swift Compiler – Concurrency build setting. With those older versions, the following behavior occurs: a nonisolated function executes off the main thread. class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() run() } private func run() { Task { await runInMainThread() } } func runInMainThread() async { print(>>>> IN runInMainThread(), Thread.isMainThread (Thread.isMainThread)) await runInBackgroundThread() } private nonisolated func runInBackgroundThread() async { print(>>>> IN runInBackgroundThread(), Thread.isMainThread (Thread.isMainThread)) } } Output: >>>> IN runInMainThread(), Thread.isMainThread true >>>> IN runInBackgroundThread(), Thread.isMainThread false However, starting with Xcode 26.2, Apple introduced the Swift Compiler – Concurrency settings. When running the same code with the d
3
0
208
3w
Query with predicate in child view running too frequently.
I'm trying to determine if this is expected swiftui behavior or an issue with SwiftUI/Data which needs a feedback request... When a child view has a Query containing a filter predicate, the query is run with each and every edit of the parent view, even when the edit has no impact on the child view (e.g. bindings not changing). In the example below, ContentView has the TextField name, and while data is being entered in it, causes the Query in AddTestStageView to be run with each character typed, e.g. 30 characters result in 30 query executions. (Need -com.apple.CoreData.SQLDebug 1 launch argument to see SQL output). Removing the filter predicate from the query and filtering in ForEach prevents the issue. In my actual use case, the query has a relatively small result set (<100 rows), but I can see this as a performance issue with the larger result sets. xcode/ios: 26.2 Repro example code: import SwiftUI import SwiftData // Repro to Query filter issue in child view running multiple time unexpectedly
1
0
80
3w
Xcode Cloud on Apple Silicon any time soon?
I'm currently using another provider for CI/CD. They've been offering Apple Silicon builds for over a year now. When we switched over, we saw our build times cut in half. I've seen similar results locally, back when I bought an M1 Mac. So, recently, I tried to use Xcode Cloud on my project. My build time is nearly 45 minutes, where my build time on my current system is about 15 minutes, max. Since I work on a team, and we make regular commits, having a 45 minute turnaround is not ideal. When I looked at the logs of my Xcode Cloud project, I saw a lot x86_64 stuff in there, which led me to believe that Xcode Cloud is still building on Intel machines. Additionally, I run tests on my builds. The build time alone (before running tests) was almost 20 minutes. The 15-minute time I cited with my current CI/CD included build time & tests running. So, a whole cycle finishes on my current setup before tests are even run. I noticed that there was a bunch of x86_64 in the logs, which made m
6
0
1.5k
3w
Xcode Cloud: All export archive steps fail with exit code 70 (Remote Mac + managed signing)
I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistrib
1
0
148
3w
Reply to Is calling different SBApplication objects from different threads bad?
First up, on the bug side, what would be most useful now would be to capture a sysdiagnose after the crash, then upload that log to the bug. A few notes on that: The log doesn't need to be collected all that soon after the bug. I try to collect within a few minutes of the crash, but there really isn't any difference triggering within the next 15+ minutes. Eventually, we start purging log data (losing data), but I've gotten useful data out of logs that were taken hours after the event. It IS important that you not reboot the machine first. Lots of data is purged during that process, to the point where I've basically found those logs useless. PLEASE include information about WHEN the problem occurred. Even better, upload the crash log from the same crash you want to use to look at in the sysdiagnose. The log volume is so high that trying to figure out what happened without a time reference can be extremely slow and time-consuming. Similarly, the crash log should be included in the sysdiagnose, but there are cas
3w
Reply to No Universal for Map App project with Tahoe
Builds Settings -> All -> Architectures: “Standard Architectures (Apple Silicon, Intel) - $(ARCHS_STANDARD) for both Debug and Release Builds Settings -> All -> Build Active Architecture Only: “No” for both Debug and Release Reinstall MacOS 26.1, Xcode 26.2. Same result: no Universal, only one platform (Silicon or Intel, never both)
3w
Xcode 9 GM Very sluggish
Just got the latest Xcode 9 (GM), and is it me or is it extremely sluggish compared to the old Xcode 8.x?Typing code seems to stagger, running the apps on the simulator seems to take a long time to start. Even the simulator is very unresponsive as well (bug reported to apple) and also screen drawing seems to messed up from time to time (for the simulator that is).I have disabled the 'source control' setting, but no effect. It is still very sluggish. Any one else experiencing this?
Replies
2
Boosts
0
Views
520
Activity
Sep ’17
Are Xcode warnings like this safe to submit (won’t disqualify)?
I’m building a Swift Playgrounds app (.swiftpm) in Xcode 26.2 and I consistently see this warning, even on brand-new Swift Playgrounds apps created from the default template: “Skipping duplicate build file in Compile Sources build phase: /Users/.../.swiftpm/Media.xcassets” Everything builds and runs normally and all images/assets appear correctly, so it seems like it’s just an annoying warning. I’ve checked for duplicates and don’t see the asset catalog listed twice, but the warning still appears whenever I add an asset catalog to any playground project in Xcode. Is this warning safe to ignore for submission, and it won’t affect Swift Student Challenge eligibility?
Replies
5
Boosts
0
Views
312
Activity
3w
Title: Developer ID + DNS Proxy system extension: profile mismatch for `com.apple.developer.networking.networkextension`
I’m building a macOS app with a DNS Proxy system extension for Developer ID + notarization, deployed via MDM, and Xcode fails the Developer ID Release build with a provisioning profile mismatch for com.apple.developer.networking.networkextension. Environment macOS: Sequoia (15.7.2) Xcode: 26.2 Distribution: Developer ID + notarization, deployed via MDM Host bundle ID: com.mydns.agent.MyDNSMacProxy DNS Proxy system extension bundle ID: com.mydns.agent.MyDNSMacProxy.dnsProxy Host entitlements (Release): File: MyDNSMacProxy/MyDNSMacProxyRelease.entitlements: http://www.apple.com/DTDs/PropertyList-1.0.dtd> com.apple.application-identifier B234657989.com.mydns.agent.MyDNSMacProxy com.apple.developer.networking.networkextension dns-proxy com.apple.developer.system-extension.install com.apple.developer.team-identifier B234657989 com.apple.security.app-sandbox com.apple.security.application-groups group.com.mydns.MyDNSmac keychain-access-groups B234657989.* xcodebuild -showBuildSettin
Replies
4
Boosts
0
Views
188
Activity
3w
Reply to Question about personal account switching to organization
The term personal account is confusing, so let me start by clarify that. The developer programme has three tiers [1]: Any Apple Account can be used for basic development. Xcode shows this as a Personal Team. This comes with significant limitations. For the details, see Developer > Support > Choosing a Membership. You can pay to join the developer programme, which makes for an Individual team. A company can pay to join the developer programme, which makes for an Organization team. You can learn more about these in Developer > Program and related pages. If you join the Individual programme you can upgrade your team to an Organization team later on. See Developer Account Helper > Membership > Updating your account information > Updating an individual membership to an organization membership. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There’s also the enterprise programme, but that’s not relevant to this threa
Replies
Boosts
Views
Activity
3w
Xcode Cloud Build times out in notarization step
We have been using Xcode Cloud Build to test an internal app. A new build is triggered automatically by a merge to main in github. Up until a few weeks ago everything was fine, we would get a notarize button and a download link. On 1/29/2026 the process started timing out at the finalizing step. The logs in the UI show no errors just a cancelled flag after 8-12 hours. Clicking the logs tab shows all green up until the step you would normally expect a stapling. Any thoughts on were to look to triage this?
Replies
1
Boosts
0
Views
222
Activity
3w
Reply to Can my submission be ran on iPhone?
Right. The submission form has two options: Swift Playground 4.6 or later Xcode 26 or later (with a note saying “Xcode app playgrounds are run in Simulator.”) In the first case, your submission must necessarily be run on an iPad. In the second, your submission will be run on the simulator, not a real device. There are some caveats here: In the first case, the Swift Playground app doesn’t yet include support for the iOS 26 SDK )-: See this thread. In the second case, the form doesn’t currently say whether it’ll be an iPhone on iPad simulator. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
3w
Swift Student Challenge 2026 submission format
Hello, I built my app in Xcode and used IOS 26 latest frameworks like Foundation Models. But some of this frameworks don't work properly in Swift Playground(MyApp.swiftpm) and cause crashes. My question is can I submit a MyApp.xcodeproj file and choose Xcode 26 as a software to run my app ? Thank you in advance.
Replies
1
Boosts
0
Views
165
Activity
3w
nonisolated Execution Differences Before and After Xcode 26.2
I have an older project that was created before Xcode 26.2. In Xcode versions prior to 26.2, there was no Swift Compiler – Concurrency build setting. With those older versions, the following behavior occurs: a nonisolated function executes off the main thread. class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() run() } private func run() { Task { await runInMainThread() } } func runInMainThread() async { print(>>>> IN runInMainThread(), Thread.isMainThread (Thread.isMainThread)) await runInBackgroundThread() } private nonisolated func runInBackgroundThread() async { print(>>>> IN runInBackgroundThread(), Thread.isMainThread (Thread.isMainThread)) } } Output: >>>> IN runInMainThread(), Thread.isMainThread true >>>> IN runInBackgroundThread(), Thread.isMainThread false However, starting with Xcode 26.2, Apple introduced the Swift Compiler – Concurrency settings. When running the same code with the d
Replies
3
Boosts
0
Views
208
Activity
3w
Query with predicate in child view running too frequently.
I'm trying to determine if this is expected swiftui behavior or an issue with SwiftUI/Data which needs a feedback request... When a child view has a Query containing a filter predicate, the query is run with each and every edit of the parent view, even when the edit has no impact on the child view (e.g. bindings not changing). In the example below, ContentView has the TextField name, and while data is being entered in it, causes the Query in AddTestStageView to be run with each character typed, e.g. 30 characters result in 30 query executions. (Need -com.apple.CoreData.SQLDebug 1 launch argument to see SQL output). Removing the filter predicate from the query and filtering in ForEach prevents the issue. In my actual use case, the query has a relatively small result set (<100 rows), but I can see this as a performance issue with the larger result sets. xcode/ios: 26.2 Repro example code: import SwiftUI import SwiftData // Repro to Query filter issue in child view running multiple time unexpectedly
Replies
1
Boosts
0
Views
80
Activity
3w
Reply to Xcode Cloud on Apple Silicon any time soon?
I imagine given Tahoe was the last release to support x86, that we'll get arm Xcode Cloud this year.
Replies
Boosts
Views
Activity
3w
Xcode Cloud on Apple Silicon any time soon?
I'm currently using another provider for CI/CD. They've been offering Apple Silicon builds for over a year now. When we switched over, we saw our build times cut in half. I've seen similar results locally, back when I bought an M1 Mac. So, recently, I tried to use Xcode Cloud on my project. My build time is nearly 45 minutes, where my build time on my current system is about 15 minutes, max. Since I work on a team, and we make regular commits, having a 45 minute turnaround is not ideal. When I looked at the logs of my Xcode Cloud project, I saw a lot x86_64 stuff in there, which led me to believe that Xcode Cloud is still building on Intel machines. Additionally, I run tests on my builds. The build time alone (before running tests) was almost 20 minutes. The 15-minute time I cited with my current CI/CD included build time & tests running. So, a whole cycle finishes on my current setup before tests are even run. I noticed that there was a bunch of x86_64 in the logs, which made m
Replies
6
Boosts
0
Views
1.5k
Activity
3w
Reply to Xcode Cloud: All export archive steps fail with exit code 70 (Remote Mac + managed signing)
I had a similar issue recently and I had to revoke the Xcode managed certs from the portal. Then it came right. I'm not sure why this happened! I think there's a limit on the number of certs you can have and something got borked?
Replies
Boosts
Views
Activity
3w
Xcode Cloud: All export archive steps fail with exit code 70 (Remote Mac + managed signing)
I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistrib
Replies
1
Boosts
0
Views
148
Activity
3w
Reply to Is calling different SBApplication objects from different threads bad?
First up, on the bug side, what would be most useful now would be to capture a sysdiagnose after the crash, then upload that log to the bug. A few notes on that: The log doesn't need to be collected all that soon after the bug. I try to collect within a few minutes of the crash, but there really isn't any difference triggering within the next 15+ minutes. Eventually, we start purging log data (losing data), but I've gotten useful data out of logs that were taken hours after the event. It IS important that you not reboot the machine first. Lots of data is purged during that process, to the point where I've basically found those logs useless. PLEASE include information about WHEN the problem occurred. Even better, upload the crash log from the same crash you want to use to look at in the sysdiagnose. The log volume is so high that trying to figure out what happened without a time reference can be extremely slow and time-consuming. Similarly, the crash log should be included in the sysdiagnose, but there are cas
Replies
Boosts
Views
Activity
3w
Reply to No Universal for Map App project with Tahoe
Builds Settings -> All -> Architectures: “Standard Architectures (Apple Silicon, Intel) - $(ARCHS_STANDARD) for both Debug and Release Builds Settings -> All -> Build Active Architecture Only: “No” for both Debug and Release Reinstall MacOS 26.1, Xcode 26.2. Same result: no Universal, only one platform (Silicon or Intel, never both)
Replies
Boosts
Views
Activity
3w