Search results for

“Xcode”

93,874 results found

Post

Replies

Boosts

Views

Activity

Xcode 26 – Organizer does not show “App Store Connect” for watchOS standalone app (only Release Testing available)
Hello, I am trying to upload a watchOS standalone app to App Store Connect using Xcode 26.3, but Organizer does not show the “App Store Connect” upload option. It only displays: • Release Testing (Ad Hoc) • Enterprise • Debugging Project setup • Target type: watchOS App (standalone, not companion) • PRODUCT_TYPE = com.apple.product-type.application • PRODUCT_BUNDLE_PACKAGE_TYPE = APPL • WRAPPER_EXTENSION = app • SUPPORTED_PLATFORMS = watchos watchsimulator • Archive configuration: Release • Base SDK: watchOS The app does not depend on iOS. Bundle ID Originally: com.example.app.watchkitapp Recreated as: com.example.app HealthKit capability enabled in: • Developer Portal • Xcode (Signing & Capabilities) Signing • Apple Distribution certificate active • App Store provisioning profile created • Manual signing configured for Release (Apple Distribution + App Store profile) • Also tested Automatic signing • Deleted old Ad Hoc profiles • Cleared Derived Data and regenerated archive App Store Co
1
0
66
Mar ’26
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
First, I wanted to apologize for not replying for a full month, as well as thank you very much for your reply. I was pulled away from this project for a couple weeks, and when I got back I was still spinning my wheels getting the driver installed. Not a problem at all. It was 67 characters and, apparently the maximum is 63. Seems like an arbitrarily short max in this day and age, and you'd think both XCode and the Developer Portal would catch that, but that's what it was. Sigh... I'm sorry I didn't think of that, as I'm aware of that limitation and actually posted about it here. FYI, you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. So, on to my current problem. The driver installs... but doesn't load. Probably because it's not matching. So I'm going to give more detailed information in the hope you can help me with this. If you haven't seen it already, I have a post here that does an extended run down of the matching
Topic: App & System Services SubTopic: Drivers Tags:
Mar ’26
Compatibility of Xcode 26.3 Release Candidate 2 and WatchOS 26.3
I have made an app using Xcode 26.3 Release Candidate 2 for my Apple Watch that runs successfully on the simulator. Xcode comes with the IoS 26.2 and WatchOS SDK 26.2. However, when I do try to connect to my device that have IoS 26.3 and watchOS 26.3, I see a succesful connection to my iPhone but I see the the world symbol and wheel keeps trying to connect on my Apple Watch. I also tried Xcode 26.4 beta 2 with no luck. I reviewed the WatchOS Release Notes: The watchOS 26.2 SDK provides support to develop watchOS apps for Apple Watch devices running watchOS 26.3. The SDK comes bundled with Xcode 26.2, available from the Mac App Store. I also tried Xcode 26.2 but no luck. Any suggestions?
1
0
177
Mar ’26
Questions about DeclaredAgeRange's isEligibleForAgeFeatures instance variable
Our team is in the process of updating our apps to comply with Texas's new state law. In order to minimize user confusion and provide the most ideal flow to access the app as possible, we have a few questions we would like answered. Summary of questions: Is isEligibleForAgeFeatures intended to be accurate and accessible before the user has accepted the Age Range permissions prompt? As other US states and/or other countries adopt a similar law going forward, will this instance variable cover those locations? Will the runtime crashes on isEligibleForAgeFeatures and other symbols in the DeclaredAgeRange framework be addressed in a future RC or in the official release? Details and Investigations: With regards to isEligibleForAgeFeatures, our team has noticed that this value is always false before the age range prompt has been accepted. This has been tested on the XCode RC 26.2 (17C48). Assuming the request needs to be accepted first, isEligibleForAgeFeatures does not get updated immediately when the user
6
0
1.2k
Mar ’26
(Xcode 26.0 → 26.2) Constant UI flickering in split view mode
Hello, I’ve been experiencing a persistent issue in Xcode since version 26.0, and it is still present in 26.2. When using the split view to display two files side by side, the area in the top‑right corner of the window (the inspector / options panel) starts flickering continuously. This happens regardless of whether I’m using the light or dark theme, and even with the Liquid Glass effect disabled in macOS settings. None of these changes have any impact on the issue. I have already submitted a bug report through Xcode (Feedback Assistant), but the issue is still present as of today. The flickering makes the interface difficult to use and visually very distracting. I’ve attached a video to clearly show the issue. I will review the attachment at the time I publish this post. Thanks in advance for any help or feedback. Video 1 https://www.icloud.com/iclouddrive/077l-R7Ybvxz89NI-B7DliEuA#xcode_bug1 Video 2 https://www.icloud.com/iclouddrive/0f6bJp48ioGRdkYiA2U4sI-cg#xcode-bug2
6
0
308
Mar ’26
Reply to (Xcode 26.0 → 26.2) Constant UI flickering in split view mode
Just in case anyone else is having a problem, I found that it flickers when I am on Studio Display + Light Theme. If I move the XCode window to the laptop display, it will not cause flickering. I have just found that on dark theme, flickering does not occur in any of my setups, whereas light theme causes flickering, just like shown in the video (top right corner). I want to repeat that: flickering only seems to happen on Studio Display for me. XCode Version: Version 26.3 (17C529) MacOS: Version 26.3 (25D125) Hardware: Apple M1 Max
Mar ’26
Reply to SwiftData Unidirectional Relationships
The error seems to be triggered the second time when a Fish is added, which is because Fish(id: 2, name: Salmon) uses a duplicate value (2) for the id attribute, which is .unique. Avoiding using a duplicate value for the .unique attribute fixes the error. I've confirmed that Xcode 26.2 (17C52) on iOS Simulator 26.2 (23C54). Best, —— Ziqiao Chen  Worldwide Developer Relations.
Mar ’26
How can I change the output dimensions of a CoreML model in Xcode when the outputs come from a NonMaximumSuppression layer?
After exerting a custom model with nms=True. In Xcode, the outputs show as: confidence: MultiArray (0 × 5) coordinates: MultiArray (0 × 4) I want to set fixed shapes (e.g., 100 × 5, 100 × 4), but Xcode does not allow editing—the shape fields are locked. The model graph shows both outputs come directly from a NonMaximumSuppression layer. Is it possible to set fixed output dimensions for NMS outputs in CoreML?
2
0
229
Mar ’26
`sysextd` rejects new `NEFilterDataProvider` activation with "no policy" on macOS 26 — despite valid Developer ID + notarization
I'm building a macOS network monitor using NEFilterDataProvider as a system extension, distributed with Developer ID signing. On macOS 26.3 (Tahoe), sysextd consistently rejects the activation request with no policy, cannot allow apps outside /Applications — despite the app being in /Applications and passing every verification check. I'm aware of the known Xcode NE signing bug (r. 108838909) and have followed the manual signing process from Exporting a Developer ID Network Extension. I've also tried both xcodebuild build and xcodebuild archive workflows — identical failure. Environment macOS 26.3 (25D125), SIP enabled Xcode 26.3 (17C529) Hardware Apple M2 Pro Certificate Developer ID Application (issued Jan 30, 2026 — 27 days old) MDM/Profiles None installed Signing & Verification (all pass) $ spctl -a -vv /Applications/Chakshu.app /Applications/Chakshu.app: accepted source=Notarized Developer ID origin=Developer ID Application: ROBIN SHARMA (R65679C4F3) $ codesign --verify --deep --stri
5
0
180
Mar ’26
Different team ID's on my certs
I've seen a few posts about this online and it seems that Xcode generates random team ID's with it's automatic signing system. But I haven't seen any way to make this work properly. If I log into the dev portal and look at my account, in the upper right I can see my team ID. If I manually generate a cert, I get a totally different one. Question: How can I generate a cert with my proper team ID (my paid account) where the ID's on my certs, identifiers and profiles all match? I've never had this issue before and am unsure how to solve it.
1
0
160
Mar ’26
Reply to Different team ID's on my certs
[quote='817211021, crewshin, /thread/817211, /profile/crewshin'] it seems that Xcode generates random team ID's with it's automatic signing system [/quote] I think you’re mixing up the various different identifiers that all use the 10-character format. See Code Signing Identifiers Explained for more about that. ps Lemme know if this helps because I’m thinking of turning this into a technote in the Inside Code Signing series, and I’m more likely to make time for that if I know that it’s actually helpful. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Mar ’26
Xcode 26 – Organizer does not show “App Store Connect” for watchOS standalone app (only Release Testing available)
Hello, I am trying to upload a watchOS standalone app to App Store Connect using Xcode 26.3, but Organizer does not show the “App Store Connect” upload option. It only displays: • Release Testing (Ad Hoc) • Enterprise • Debugging Project setup • Target type: watchOS App (standalone, not companion) • PRODUCT_TYPE = com.apple.product-type.application • PRODUCT_BUNDLE_PACKAGE_TYPE = APPL • WRAPPER_EXTENSION = app • SUPPORTED_PLATFORMS = watchos watchsimulator • Archive configuration: Release • Base SDK: watchOS The app does not depend on iOS. Bundle ID Originally: com.example.app.watchkitapp Recreated as: com.example.app HealthKit capability enabled in: • Developer Portal • Xcode (Signing & Capabilities) Signing • Apple Distribution certificate active • App Store provisioning profile created • Manual signing configured for Release (Apple Distribution + App Store profile) • Also tested Automatic signing • Deleted old Ad Hoc profiles • Cleared Derived Data and regenerated archive App Store Co
Replies
1
Boosts
0
Views
66
Activity
Mar ’26
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
First, I wanted to apologize for not replying for a full month, as well as thank you very much for your reply. I was pulled away from this project for a couple weeks, and when I got back I was still spinning my wheels getting the driver installed. Not a problem at all. It was 67 characters and, apparently the maximum is 63. Seems like an arbitrarily short max in this day and age, and you'd think both XCode and the Developer Portal would catch that, but that's what it was. Sigh... I'm sorry I didn't think of that, as I'm aware of that limitation and actually posted about it here. FYI, you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. So, on to my current problem. The driver installs... but doesn't load. Probably because it's not matching. So I'm going to give more detailed information in the hope you can help me with this. If you haven't seen it already, I have a post here that does an extended run down of the matching
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Mar ’26
Reply to Compatibility of Xcode 26.3 Release Candidate 2 and WatchOS 26.3
Found out that best way to load new app to Watch is to load first the companion app on the iphone, then to the watch. The globe symbol on Xcode for the watch is expected since it is not directly connected to Xcode but it is via iphone.
Replies
Boosts
Views
Activity
Mar ’26
Compatibility of Xcode 26.3 Release Candidate 2 and WatchOS 26.3
I have made an app using Xcode 26.3 Release Candidate 2 for my Apple Watch that runs successfully on the simulator. Xcode comes with the IoS 26.2 and WatchOS SDK 26.2. However, when I do try to connect to my device that have IoS 26.3 and watchOS 26.3, I see a succesful connection to my iPhone but I see the the world symbol and wheel keeps trying to connect on my Apple Watch. I also tried Xcode 26.4 beta 2 with no luck. I reviewed the WatchOS Release Notes: The watchOS 26.2 SDK provides support to develop watchOS apps for Apple Watch devices running watchOS 26.3. The SDK comes bundled with Xcode 26.2, available from the Mac App Store. I also tried Xcode 26.2 but no luck. Any suggestions?
Replies
1
Boosts
0
Views
177
Activity
Mar ’26
Questions about DeclaredAgeRange's isEligibleForAgeFeatures instance variable
Our team is in the process of updating our apps to comply with Texas's new state law. In order to minimize user confusion and provide the most ideal flow to access the app as possible, we have a few questions we would like answered. Summary of questions: Is isEligibleForAgeFeatures intended to be accurate and accessible before the user has accepted the Age Range permissions prompt? As other US states and/or other countries adopt a similar law going forward, will this instance variable cover those locations? Will the runtime crashes on isEligibleForAgeFeatures and other symbols in the DeclaredAgeRange framework be addressed in a future RC or in the official release? Details and Investigations: With regards to isEligibleForAgeFeatures, our team has noticed that this value is always false before the age range prompt has been accepted. This has been tested on the XCode RC 26.2 (17C48). Assuming the request needs to be accepted first, isEligibleForAgeFeatures does not get updated immediately when the user
Replies
6
Boosts
0
Views
1.2k
Activity
Mar ’26
(Xcode 26.0 → 26.2) Constant UI flickering in split view mode
Hello, I’ve been experiencing a persistent issue in Xcode since version 26.0, and it is still present in 26.2. When using the split view to display two files side by side, the area in the top‑right corner of the window (the inspector / options panel) starts flickering continuously. This happens regardless of whether I’m using the light or dark theme, and even with the Liquid Glass effect disabled in macOS settings. None of these changes have any impact on the issue. I have already submitted a bug report through Xcode (Feedback Assistant), but the issue is still present as of today. The flickering makes the interface difficult to use and visually very distracting. I’ve attached a video to clearly show the issue. I will review the attachment at the time I publish this post. Thanks in advance for any help or feedback. Video 1 https://www.icloud.com/iclouddrive/077l-R7Ybvxz89NI-B7DliEuA#xcode_bug1 Video 2 https://www.icloud.com/iclouddrive/0f6bJp48ioGRdkYiA2U4sI-cg#xcode-bug2
Replies
6
Boosts
0
Views
308
Activity
Mar ’26
Reply to (Xcode 26.0 → 26.2) Constant UI flickering in split view mode
Just in case anyone else is having a problem, I found that it flickers when I am on Studio Display + Light Theme. If I move the XCode window to the laptop display, it will not cause flickering. I have just found that on dark theme, flickering does not occur in any of my setups, whereas light theme causes flickering, just like shown in the video (top right corner). I want to repeat that: flickering only seems to happen on Studio Display for me. XCode Version: Version 26.3 (17C529) MacOS: Version 26.3 (25D125) Hardware: Apple M1 Max
Replies
Boosts
Views
Activity
Mar ’26
Reply to SwiftData Unidirectional Relationships
The error seems to be triggered the second time when a Fish is added, which is because Fish(id: 2, name: Salmon) uses a duplicate value (2) for the id attribute, which is .unique. Avoiding using a duplicate value for the .unique attribute fixes the error. I've confirmed that Xcode 26.2 (17C52) on iOS Simulator 26.2 (23C54). Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Mar ’26
Preview crashes consistency in Xcode 16 beta
In the first Xcode 16 beta, none of my SwiftUI previews work - they all just crash on start up. Has anybody run into this and found a workaround? Have tried all the usual steps of cleaning the project/restarting Xcode.
Replies
30
Boosts
0
Views
12k
Activity
Mar ’26
Reply to Preview crashes consistency in Xcode 16 beta
Had the same problem with Firebase packages causing a crash in Xcode 16 26.4 beta and setting Editor -> Canvas -> Use Legacy Previews Execution fixed it.
Replies
Boosts
Views
Activity
Mar ’26
Reply to How can I change the output dimensions of a CoreML model in Xcode when the outputs come from a NonMaximumSuppression layer?
Thanks for the suggestions. I was just wondering if it’s possible to make edits on directly in the Xcode editor.
Topic: Machine Learning & AI SubTopic: Core ML Tags:
Replies
Boosts
Views
Activity
Mar ’26
How can I change the output dimensions of a CoreML model in Xcode when the outputs come from a NonMaximumSuppression layer?
After exerting a custom model with nms=True. In Xcode, the outputs show as: confidence: MultiArray (0 × 5) coordinates: MultiArray (0 × 4) I want to set fixed shapes (e.g., 100 × 5, 100 × 4), but Xcode does not allow editing—the shape fields are locked. The model graph shows both outputs come directly from a NonMaximumSuppression layer. Is it possible to set fixed output dimensions for NMS outputs in CoreML?
Replies
2
Boosts
0
Views
229
Activity
Mar ’26
`sysextd` rejects new `NEFilterDataProvider` activation with "no policy" on macOS 26 — despite valid Developer ID + notarization
I'm building a macOS network monitor using NEFilterDataProvider as a system extension, distributed with Developer ID signing. On macOS 26.3 (Tahoe), sysextd consistently rejects the activation request with no policy, cannot allow apps outside /Applications — despite the app being in /Applications and passing every verification check. I'm aware of the known Xcode NE signing bug (r. 108838909) and have followed the manual signing process from Exporting a Developer ID Network Extension. I've also tried both xcodebuild build and xcodebuild archive workflows — identical failure. Environment macOS 26.3 (25D125), SIP enabled Xcode 26.3 (17C529) Hardware Apple M2 Pro Certificate Developer ID Application (issued Jan 30, 2026 — 27 days old) MDM/Profiles None installed Signing & Verification (all pass) $ spctl -a -vv /Applications/Chakshu.app /Applications/Chakshu.app: accepted source=Notarized Developer ID origin=Developer ID Application: ROBIN SHARMA (R65679C4F3) $ codesign --verify --deep --stri
Replies
5
Boosts
0
Views
180
Activity
Mar ’26
Different team ID's on my certs
I've seen a few posts about this online and it seems that Xcode generates random team ID's with it's automatic signing system. But I haven't seen any way to make this work properly. If I log into the dev portal and look at my account, in the upper right I can see my team ID. If I manually generate a cert, I get a totally different one. Question: How can I generate a cert with my proper team ID (my paid account) where the ID's on my certs, identifiers and profiles all match? I've never had this issue before and am unsure how to solve it.
Replies
1
Boosts
0
Views
160
Activity
Mar ’26
Reply to Different team ID's on my certs
[quote='817211021, crewshin, /thread/817211, /profile/crewshin'] it seems that Xcode generates random team ID's with it's automatic signing system [/quote] I think you’re mixing up the various different identifiers that all use the 10-character format. See Code Signing Identifiers Explained for more about that. ps Lemme know if this helps because I’m thinking of turning this into a technote in the Inside Code Signing series, and I’m more likely to make time for that if I know that it’s actually helpful. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
Mar ’26