xcode github

[quote='872058022, Youssef-Hammad, /thread/812425?answerId=872058022#872058022, /profile/Youssef-Hammad'] I tried changing the icon of the app after installation and it somehow breaks the signature. [/quote] Indeed. And that’s not a mystery at all. In general, changing content within an app’s bundle will break the seal on the code signature. If you’re curious how that all works, see TN3126 Inside Code Signing: Hashes. But a custom icon is special. You can apply a custom icon to an app without breaking its signature. To see this in action, go to Finder, select your app, choose File > Get Info, select the icon, and paste in an image. I regularly do this with older Xcode versions. For example, my main Xcode is currently Xcode 26.2, but I have Xcode 16.4 around for testing. I apply a custom icon to that older Xcode to help head of the confusion that inevitably occurs when you have multiple versions of Xcode running. If you dig into the on-disk results of th

Notarisation is a read-only process, so notarising an app can’t cause it to stop working. Usually problems like this are caused by the hardened runtime. Notarisation requires that you enable the hardened runtime, so folks re-sign their app with that enabled and then it fails. There are two ways you can approach that: Run the Developer ID-signed build before you notarise it. This should hang in the same way. Enable the hardened runtime on your day-to-day development builds. This lets you debug this issue like you would any other hang. Resolving Trusted Execution Problems has a section on debugging hardened runtime issues, namely Resolving Hardened Runtime Incompatibilities. Oh, one more thing. This is problematic: codesign --force --deep --verify --verbose --option runtime --sign Developer ID Application: ORG NAME (ZZZZZZZZZ) path/to/app.app To start, you’re supplying both --verify and --sign, which is never a good idea. For any given invocation of codesign, you should do one or the other. Next, when signing,

[quote='812624021, joel2001k, /thread/812624, /profile/joel2001k'] My certificates expired and I created new ones. [/quote] How? Using the Developer website? Or using Xcode? Because… [quote='812624021, joel2001k, /thread/812624, /profile/joel2001k'] How to fix the missing private key? [/quote] The way that you create a signing certificate determines where your private key ends up. For most certificates it’s just to just revoke stuff and start again, and that’s often the easiest way to resolve issues like this. WARNING That’s not the case for Developer ID certificates. For those, see The Care and Feeding of Developer ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='812598021, yccheok, /thread/812598, /profile/yccheok'] Is nonisolated still an appropriate way to ensure code runs on a background thread? [/quote] Yes and no. There are a couple of Swift Evolution proposals that describe this change in detail: SE-0461 Run nonisolated async functions on the caller's actor by default SE-0466 Control default actor isolation inference And, as you’ve noticed, there are Xcode build settings that affect this stuff. So, you have a couple of options: You can tweak your build settings and leave your code as is. Or you can move forward to the new build settings and tweak your code. I generally favour the second option, but I can understand folks preferring the first option, especially when wrangling a large project. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not sure what you’re asking for here. Are you trying to report a bug against Xcode? Or trying to work out how to use expectation-based tests in Swift Testing? If it’s the former, I recommend that you do that officially, as explained in Bug Reporting: How and Why? And please post your bug number, just for the record. If it’s the latter, see Expectations and confirmations. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi all, we do have the same problem. Me and several other colleagues. We just found out the same that iOS Simulator version 18.2 is the latest working for us. We have also tried to clean everything and start the installation from scratch. It did not help. I throw my stack trace here as well in the hope it might be seen and it might help some developer at Apple. Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = 2026-01-14 08:42:36 +0000; IDERunOperationFailingWorker = _IDEInstalliPhoneSimulatorWorker; Session = com.apple.CoreSimulator.SimDevice.79733B3C-A5BA-41E8-A88A-6DA408E517D6; } -- Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding Domain: com.apple.SimLaunchHostService.RequestError Code: 4 -- Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { device_identifier = XXX; device_model = iPhone17,5; device_osBuild = 26.0 (23A339); device_osBuild_monotoni

Also hitting this error on Xcode Version 26.0 (17A321) and iPhone simulator running iOS 26.0 (23A343)

@MadBha @Divyajain Investigating this, we found out that what you are describing with the second accessory setup causing power state change, was a known issue with iOS 18, but has since been fixed in iOS 26. If you are seeing this issue with iOS 26, then we will need some diagnostic logs to understand what might be happening. To help our Bluetooth team to investigate this issue, we'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do. FIrst, to create a diagnostic log, please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Accessory Setup Kit for iOS< and Bluetooth for iOS to install those logging profiles on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And then attach that to the bug report as well. Bug Reporting: How and Why? has tips on creating a successful bug report. Importa

So in this context an app distributed by test flight would be the same an app distributed in xcode?