xcode github

Hi, Did you create a new CSR? Or re-submit an existing one? I run openssl and then on apple developer I have edited the certificate and submitted the new CSR. openssl genrsa -out ALDencryption.key 2048 openssl req -new -key ALDencryption.key -out csr2048ALDEncrypt.certSigningRequest -subj /emailAddress=****, CN=****, C=CH openssl genrsa -out ALDsigning.key 2048 openssl req -new -key ALDsigning.key -out csr2048ALDSigning.certSigningRequest -subj /emailAddress=****, CN=****, C=CH Then I downloaded the certificates and installed them. Provisioning profiles authorise, amongst other things, specific code-signing certificates. If you create a new certificate, you need to regenerate your profile. Xcode generates usually the embedded provisioning profile, but my Xcode setup isn't working. The archive action fails. I build from my makefile all dependencies so there are build directories for arm64, x86_64 and the final universal app build from make. I am unsure what Xcode actually does? Last

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. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

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. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Is it acceptable to include placeholders for features that aren’t supported by Swift Playgrounds, or features I planned but didn’t have time to fully implement (as long as the core experience works)? IMHO, that would be a bad idea, even if it were not forbidden; what would be the value for reviewer? My app relies a lot on user inputs. Is it okay to include a button that loads sample data for reviewers, or is there a preferred approach for this? App must be tested in 3 minutes. No time for a lot of user data. So, providing demo data may be a workaround, but capability to enter personal data is part of user experience. Couldn't you have some predefined (but modifiable) data but let user enter a few (less than 10) important data to experiment your app ? Besides the known constraints (< 25 MB, experienceable within ~3 minutes), are there any other limits, e.g. lines of code or overall app complexity All requirements are in the terms and conditions for submission. Read them carefully. If I remember well, there

Downgrading to Xcode 26.1 worked around the problem for me.

Yesterday, January 14, I installed Xcode 26.2 from XcodeReleases. The issue is still present on iPhone 12 mini and iPhone 13 mini devices.

Hello @isaacweisberg, UIKit has its own .animate you can use on observed changes of .preferredContentSize, which reflects the view's current size. For more information, ⌘+Click on a .UIHostingController in Xcode to read through the DocC comments that provides much context.  Travis Trotto - DTS Engineer

For all of these weird errors, you'll need a matching Xcode version, Simulator version, and macOS version for everything to work. You also need all versions to be at least 26.0, otherwise the model assets simply aren't there. e.g. Xcode 26.2, iOS 26.2 simulator, macOS 26.2 Hi there I started seeing this after I updated my Mac (and XCode) to 26.2. To clarify, are you saying that I must use iOS version 26.2 with in Simulator if I am developing with Foundation Models now? I have been developing my app for iOS 26.0 and above and all of my calls to Foundation Models now give this error. I can't develop for 26.0 now? That doesn't seem right.

I … uploaded a Certificate Signing Request using web form. Did you create a new CSR? Or re-submit an existing one? What about the provisioning profile? Provisioning profiles authorise, amongst other things, specific code-signing certificates. If you create a new certificate, you need to regenerate your profile. If you’re curious how this actually works, see: TN3125 Inside Code Signing: Provisioning Profiles TN3161 Inside Code Signing: Certificates [quote='872512022, joel2001k, /thread/812624?answerId=872512022#872512022, /profile/joel2001k'] I would expect to be able to add Mac Application Distribution in Xcode Manage Certificates, but it is missing. [/quote] Indeed. And you should choose Apple Distribution. Historically we used to issue separate iOS and macOS code-signing certificates. There are still bits of that past world lurking in various subsystems, but in most cases these days you want to use the generic stuff, meaning Apple Development and Apple Distribution. [quote='872512022, joel2001k, /t

OK, so definitely not your project. If you temporarily remove the iCloud key-value storage capability capability, the app builds, right? If so, look in the build log for an entry like this: CodeSign …/Test811382.app (in target 'Test811382' from project 'Test811382') cd …/Test811382 Signing Identity: Apple Development: Quinn Quinn (7XFU7D52S4) Provisioning Profile: iOS Team Provisioning Profile: com.example.apple-samplecode.Test811382 (5db3ba83-07fb-4780-8ca4-f87de64fd20d) Note For info on how to get the build log, see Command [something] failed with a nonzero exit code. The UUID in that entry is the UUID of the provisioning profile that Xcode is using to sign your app. You should find that in ~/Library/Developer/Xcode/UserData/Provisioning Profiles. Now dump the contents of that profile like so: % security cms -D -i 5db3ba83-07fb-4780-8ca4-f87de64fd20d.mobileprovision | plutil -p - { … Entitlements => { application-identifier => SKMME9E2Y8.com.example.apple-samplecode.Test811382 com.ap

SOLUTION: Delete workspace user state files If Xcode crashes when opening the AI Intelligence tab in a specific project, the issue is corrupted UI state data in your workspace. Fix: Close Xcode completely Navigate to your project directory in Terminal and delete UserInterfaceState.xcuserstate: rm YourProject.xcodeproj/project.xcworkspace/xcuserdata/YOUR_USERNAME.xcuserdatad/UserInterfaceState.xcuserstate This resolved the crash for me in Xcode 26.2 on macOS 26.2. What this does: Deletes the corrupted workspace UI state (including Intelligence chat history). Xcode will recreate it fresh. You'll lose panel positions and open tabs, but all your code and project settings remain intact.