“Xcode”

By watchOS standalone app, did you mean watch-only app, with the terminology defined in TN3157? For a watch-only app, it does seem that Xcode 26.x doesn't provide the App Store Connect option in the app archiving process, which, to me, is likely a bug. Do you have a feedback report yet? If not, would you mind to file one with screenshots that show the steps you use to create and archive a project, and then share your report ID here? Thanks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

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

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.

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

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.

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.

Thanks for the suggestions. I was just wondering if it’s possible to make edits on directly in the Xcode editor.

[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

The macOS 15 development cycle triggered a bunch of changes in app groups. See App Groups: macOS vs iOS: Working Towards Harmony for the backstory. Going forward, I recommend that you: Decide on the app group ID you want to use. This can use either the macOS style or iOS style. For new code I recommend the iOS style, although if you have an exist product that uses the macOS style it usually makes sense to stick with that. For each program involved (so your app and your file provider appex)… Make sure it has an explicit App ID. Create a profile that authorises that App ID to access your app group. Make sure that profile gets embedded in the program’s bundle. Sign the program to claim access to that app group. IMPORTANT Make sure to sign the program with com.apple.application-identifier so that the system can associated the program with its provisioning profile. If you’re using Xcode, it will typically take care of this for you, although my experience is that this works better if you’re using an iOS st