Search results for

xcode github

94,695 results found

Post

Replies

Boosts

Views

Activity

Signed app can't be verified
I've signed an app, zipped it, and uploaded it to github. When I download it on another Mac, I get it can't be opened because it could not be verified for malware. But on that computer, I can verify it with codesign, and it appears to be correct (as far as I can tell). I can copy/paste the app from my other Mac, and that copy will run without problem. sys_policy, however, gives: Notary Ticket Missing File: ReView.app Severity: Fatal Full Error: A Notarization ticket is not stapled to this application. Type: Distribution Error This is the same for the copy that runs, and the copy that doesn't. The difference between them appears to be a quarantine xattr. I can delete this, and the app launches without incident. Is this expected? Why should a signed app be quarantined just because it's been downloaded? The whole point of paying the fee is to avoid the security obstacles...! ;-)
3
0
648
1w
NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension
Hi there, I have an SwiftUI app that opens a user selected audio file (wave). For each audio file an additional file exists containing events that were extracted from the audio file. This additional file has the same filename and uses the extension bcCalls. I load the audio file using FileImporter view modifier and within access the audio file with a security scoped bookmark. That works well. After loading the audio I create a CallsSidecar NSFilePresenter with the url of the audio file. I make the presenter known to the NSFileCoordinator and upon this add it to the FileCoordinator. This fails with NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension for; Error Domain=NSPOSIXErrorDomain Code=3 No such process My Info.plist contains an entry for the document with NSIsRelatedItemType set to YES I am using this kind of FilePresenter code in various live apps developed some years ago. Now when starting from scratch on a fresh macOS26 system with most current Xcode I do not manage to get
7
0
211
1w
Xcode crashing in live view
I'm new to Xcode. I just downloaded version 26.2 and I'm working on an iMac with macOS Sequoia 15.7.3. I'm created a playground with some very simple code and it crashes when I click live view. I tried looking all over online for a solution and nothing has worked. I tried uninstalling and reinstalling Xcode and still have the same problem. When running the code with the console open I do see the following error. objc[19786]: Class _TtC16AppIntentSchemas16AppIntentDomains is implemented in both /System/Library/PrivateFrameworks/AppIntentSchemas.framework/Versions/A/AppIntentSchemas (0x2840a4c28) and /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/AppIntentSchemas.framework/Versions/A/AppIntentSchemas (0x3276359e8). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. I went to the first folder mentioned in the error /System/Library/PrivateFrameworks/AppIntentSchemas.framework
2
0
65
1w
Reply to XCode26.2 ld: Assertion failed: ((ct == Atom::ContentType::objcConst) || (ct == Atom::ContentType::objcData) || (ct == Atom::ContentType::constData) || (ct == Atom::ContentType::constText)), function ObjCClassReadOnlyDataRef, file Atom.cpp, line 329
Thanks for this very interesting post. I'm not an expert in this field and I invite experts to comment, in my modest opinion, It looks like there’s something unexpected with ObjC/Swift metadata. Can we ask them for a focused sample project that reproduces the issue, can you make a copy of the project that is causing the issue, and then remove everything that isn’t important to keep the meta data in the project that may be causing this? Maybe the linker error you're encountering in Xcode 26.2 after migrating from Xcode 16.2, along with the modifications you've made to the linker flags, points to a deeper issue with how object files are being processed, specifically related to Objective-C runtime data. Could that mean or indicates there is an incompatibility or corruption in Objective-C metadata? Any object files or libraries you're linking were compiled with an older compiler version? Any external libraries or frameworks, with the Xcode 26.2 compiler. If you're using CocoaPods or Car
1w
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
Having the same issue, Macos Tahoe 26.2, i tried everything i found on net: deleting caches, all xcode files, reinstalling it, rebooting my computer, deleting all simalator devices, deleting IOS from Xcode => setting components, downloading it again. I tried installing older IOS, no help, when starting emulator i have this error: Unable to boot the Simulator And this error, when i'm trying to do this from terminal == Devices == -- iOS 26.2 -- iPhone 17 Pro (1FC8FFC9-A04D-434B-85F0-F5AE2DB4CDAC) (Shutdown) iPhone 17 Pro Max (71761C54-D406-496E-A552-CD72FACD10DA) (Shutdown) iPhone Air (64607ACA-F580-4A6A-A816-1AD1E8BEBC32) (Shutdown) iPhone 17 (7ECEC4C0-0DC9-4B5A-A9A0-05E4B1038C68) (Shutdown) iPhone 16e (A175B467-438D-41A7-B537-D7E23B4FFF21) (Shutdown) iPad Pro 13-inch (M5) (FA74F9C7-93C9-40D6-86F5-74E46FCCF7EC) (Shutdown) iPad Pro 11-inch (M5) (73A17C77-DBFA-4748-880D-15FBBE43E57E) (Shutdown) iPad mini (A17 Pro) (09BF89D2-640C-4083-937A-4859633BB69E) (Shutdown) iPad (A16) (5FF5869B-042F-48
1w
Reply to Linker nondeterminism (ld_new) involving branch islands
[quote='873554022, jamie_sq, /thread/805609?answerId=873554022#873554022, /profile/jamie_sq'] if any investigation has revealed whether there's anything that can be done to work around the problem [/quote] Nothing obvious popped out )-: I can say that we do fully understand the issue now and that makes the likelihood of a fix promising. However, I can’t offer a concrete timeline, other than to confirm that the fix didn’t catch the Xcode 26.2 bus. As always, I recommend that you re-test with future beta releases of Xcode as we seed them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Credential Provider Extension should allow BE=0, BS=0 for device-bound passkeys
In these threads, it was clarified that Credential Provider Extensions must set both Backup Eligible (BE) and Backup State (BS) flags to 1 in authenticator data: https://developer.apple.com/forums/thread/745605 https://developer.apple.com/forums/thread/787629 However, I'm developing a passkey manager that intentionally stores credentials only on the local device. My implementation uses: kSecAttrAccessibleWhenUnlockedThisDeviceOnly for keychain items kSecAttrTokenIDSecureEnclave for private keys No iCloud sync or backup These credentials are, by definition, single-device credentials. According to the WebAuthn specification, they should be represented with BE=0, BS=0. Currently, I'm forced to set BE=1, BS=1 to make the extension work, which misrepresents the actual backup status to relying parties. This is problematic because: Servers using BE/BS flags for security policies will incorrectly classify these as synced passkeys Users who specifically want device-bound credentials for higher security cannot get accu
0
0
606
1w
XCode26.2 ld: Assertion failed: ((ct == Atom::ContentType::objcConst) || (ct == Atom::ContentType::objcData) || (ct == Atom::ContentType::constData) || (ct == Atom::ContentType::constText)), function ObjCClassReadOnlyDataRef, file Atom.cpp, line 329
Dear Apple engineers: My previous project was successfully compiled using Xcode 16.2. Now, I need to adapt it to Xcode 26. I know that the linker in Xcode 26 has undergone significant changes. So, in the 'Other Linker Flags' configuration of the Build Settings in the project engineering of Xcode 26.2, I deleted '-ld64' and added '-Xlinker -dead_strip -Xlinker -dead_strip -allow_dead_duplicates' to adapt to the new linker of Xcode 26. After the modification, when I compiled my project engineering using Xcode 26.2 compiler, I encountered a new linker error. The error log is attached. Regarding this error, how should we solve it? Thank you. XCode26.2BuildErrorLog.txt
3
0
121
1w
Reply to Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected)
Inside System : Library I have the folder AssetsV2 with large Folders. com_apple_MobileAssest_iOSSimulatorRuntime 85.83 GB and .com_apple_MobileAssest_xrOSSimulatorRuntime 56.23 GB. Also _appleTVOS.. 21.41 GB and _watchOS.. 18.87 GB. I've tried xcrun simctl runtime list and delete. After a computer restart xcrun reported Total Disk Images dropping from 267.9G to 106.8G BUT no change to Finder reported sizes. DaisyDisk showed 99G free and now 240G or 68G A lot of disk images appear in Disk Utility but eject doesn't work for most of them, maybe none. In Xcode I see a lot of simulators. I was able to delete many of them but no change to memory reported by the Finder. It looks like I've tried the suggestions above. I've run out of ideas.
1w
Reply to Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected)
I am encoutering the same problem with a universal iOS simulator version (18.5) Because the old version (18.5) is missing from this XML, Xcode and mobileassetd seem to have lost track of it entirely. I managed to get Xcode to recognise it, but Xcode chooses to soft delete instead of ing the disk. Running scan-and-mount identifies the orphan simulator: > xcrun simctl runtime scan-and-mount > xcrun simctl runtime list == Disk Images == -- iOS -- iOS 26.2 (23C54) - E2B78652-EDF6-450D-BC2C-2F0B11B3AD95 (Ready) -- unknown -- - CE40DFD4-ACAC-4A6B-975A-51148DA604B0 (Verifying) Total Disk Images: 2 (7.8G) [Note: 1 image(s) are of unknown size] > xcrun simctl runtime list == Disk Images == -- iOS -- iOS 18.5 (22F77) - CE40DFD4-ACAC-4A6B-975A-51148DA604B0 (Ready) iOS 26.2 (23C54) - E2B78652-EDF6-450D-BC2C-2F0B11B3AD95 (Ready) Total Disk Images: 2 (7.8G) [Note: 1 image(s) are of unknown size] Then I tried to directly delete the simulator: > xcrun simctl runtime delete 22F77 > x
1w
Sharing My Experience in Developing an SSL Certificate Monitoring Website
Hi everyone, recently I used codex and GPT-5.2 to build a simple SSL certificate monitoring website, and I'd like to share some of my development experiences. The project link is at the end, but first, let's talk about the technical implementation. The Motivation I've encountered several service outages caused by expired SSL certificates in the past. Each time, I had to react after users reported the issue, which was very passive. While there are some monitoring tools on the market, they are either too heavy or lack the necessary features, so I decided to build my own. Technology Stack Next.js 16 + shadcn/ui + TypeScript I chose Next.js because: The development experience with App Router is excellent, with a clear mapping between routes and file structure. Server Components reduce the need for client-side JavaScript. Built-in features like image optimization and font loading are ready to use out of the box. shadcn/ui is a component library based on Radix UI, and its advantages are: Components are copied direc
0
0
169
1w