dsym file

QuickLookAR shares the actual USDZ model instead of the original website URL — critical copyright and data leak issue on iOS 26 Since iOS 26, QuickLookAR (or ARQuickLookPreviewItem) no longer preserves the original web URL when sharing a model. Instead of sending the link to the hosted file, the system directly shares the actual USDZ model file with the recipient. This is a critical regression and a severe breach of intellectual property protection, as it exposes proprietary 3D models that must never be distributed outside of the controlled web environment. In earlier iOS versions (tested up to iOS 18), QuickLookAR correctly handled sharing — the share sheet would send the website link where the model is hosted, not the file itself. Starting with iOS 26, this behavior has changed and completely breaks the intended secure flow for AR experiences. Our project relies on allowing users to view models in AR via QuickLook, without ever transferring the underlying 3D assets. Now, the share

Original Problem We use codesign and notarytool in a scripted environment to build and distribute binaries daily. We also do manual builds by logging into the build server using SSH. This has been working for many years, but after updating to a new Developer ID Application certificate, codesign was failing with errSecInternalComponent and the console logs showed errSecInteractionNotAllowed. Summary of Resolution Attempting to fix the problem resulted in multiple copies of the same Certificate which were NOT shown by Keychain Access. I had to run security delete-identity multiple times to clear out the redundant Identities and then imported the certificate using the security CLI tool. Details I originally followed these instructions for requesting and installing a new certificate: https://developer.apple.com/help/account/certificates/create-developer-id-certificates/ Tip: Use the security tool intead These instructions fail to mention two critical points: 1) they assume the machine you generate the request on

Hi everyone, I am attempting to generate an Ad Hoc provisioning profile for my iOS app that includes MusicKit capabilities, but the generated .mobileprovision file consistently lacks the required entitlement, despite the configuration appearing correct in the developer portal. The Issue: I have enabled MusicKit under the App Services tab for my App ID. I have saved this configuration, verified it is checked in the UI, and then regenerated and downloaded my provisioning profile. However, when I inspect the internal contents of the .mobileprovision file, the Entitlements dictionary does not contain the com.apple.developer.music-kit key. It only contains the standard keys (Team ID, App ID, etc.). Steps Taken: Created a brand new App ID to rule out legacy data issues. Explicitly enabled MusicKit under the App Services tab for this new identifier. Created a fresh Ad Hoc Distribution profile linked to this new ID. Downloaded the profile and inspected the file structure: the MusicKit entit

Hi! I would like to experiment with the Accessory Setup Kit, but I am not sure how I can add the required entitlement to my Apple Developer account. I added the following to the plist file: NSAccessorySetupKitSupports WiFi NSAccessorySetupWiFiSSIDPrefix test_ test And the following to the entitlements file: com.apple.developer.accessory-setup-kit But I am unable to build as my provisioning profile doesn't include com.apple.developer.accessory-setup-kit entitlement. On the developer portal, I navigated to “Certificates, Identifiers & Profiles” > “Identifiers” > “”, but I don't see it under Capabilities or App services, nor under requests. How do I configure my profile so that I am able to make use of this kit?

Hi everyone, I’m new to the Apple Developer side of things and I want to make sure I’m handling this correctly. I hired a freelance iOS developer to build my app. I have my own Apple Developer account (Individual), and I want the app published under my account. The developer says he needs me to create a Certificate Signing Request (CSR), then he will generate the distribution certificate on his end and send me the .cer file back. From there, he would use that for signing and submitting the app. My questions: 1. Is this the correct and modern way to handle app signing? 2. Should I instead just add him to my App Store Connect account with Developer access and let him manage signing through Xcode? Dev claims this won’t work, which I haven’t been able to prove or disprove. ChatGPT says it does,but other AI tools says it doesn’t. 3. Is there any risk in sharing certificates like this? 4. What is considered best practice in 2026 for working with freelancers while keeping full control of the account? My goa

Device: iPhone (real device) iOS: 17.x Permission: Granted Notifications are scheduled using UNCalendarNotificationTrigger. The function runs and prints SCHEDULING STARTED. However, notifications never appear at 8:00 AM, even the next day. Here is my DailyNotifications file code: import Foundation import UserNotifications enum DailyNotifications { // CHANGE THESE TWO FOR TESTING / PRODUCTION // For testing set to a few minutes ahead static let hour: Int = 8 static let minute: Int = 0 // For production use: // static let hour: Int = 9 // static let minute: Int = 0 static let daysToSchedule: Int = 30 private static let idPrefix = daily-thought- private static let categoryId = DAILY_THOUGHT // MARK: - Permission static func requestPermission(completion: @escaping (Bool) -> Void) { let center = UNUserNotificationCenter.current() center.requestAuthorization(options: [.alert, .sound]) { granted, _ in DispatchQueue.main.async { completion(granted) } } } // MARK: - Schedule static func scheduleNext30Days(