Search results for

dsym file

77,692 results found

Post

Replies

Boosts

Views

Activity

Reply to In-App Provisioning
Thanks for that!! Very useful, I would review each string as the NSExtensionPrincipalClass does not look correct to me but is set by Xcode, but it's been a while since I create an extension, I should try today to create a new one to see how it works. I'll invite extension experts to look at your configuration. As Xcode sets your string must be correct, just make sure the method get called? $(PRODUCT_MODULE_NAME).handler.... https://developer.apple.com/documentation/BundleResources/Information-Property-List/NSExtension/NSExtensionPrincipalClass NSExtensionPointIdentifier com.apple.passkit.issuer-provisioning NSExtensionPrincipalClass $(PRODUCT_MODULE_NAME).IssuerExtensionHandler https://developer.apple.com/documentation/bundleresources/managing-your-app-s-information-property-list#Manually-supply-an-information-property-list-file https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/AppExtensionKeys.html So it I follow the documentation it seems c
4w
Reply to In-App Provisioning
Thanks for responding. Yes, I requested form Apple, I got the entitlement identifier and I configure the entitlement files aps-environment development com.apple.developer.pass-type-identifiers $(TeamIdentifierPrefix)pass.com.example.example com.apple.developer.payment-pass-provisioning Both from the main project and the wallet extension and this is my Info.plist form the wallet extension NSExtension NSExtensionPointIdentifier com.apple.passkit.issuer-provisioning NSExtensionPrincipalClass $(PRODUCT_MODULE_NAME).IssuerExtensionHandler
4w
Reply to iOS 26.2 Safari back button fails to re-open tab with same target
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. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Safari & Web SubTopic: General Tags:
4w
Reply to In-App Provisioning
Thanks for the post. Can you provide more information for developers to comment about the configuration and if you have followed the extension implementation? When you mentioned that you have the entitlement identifier, could you please provide more details on where you obtained it? Have you made a request for it from Apple? Domain: IXUserPresentableErrorDomain Code: 1 ... NSExtensionPointIdentifier The error message you are encountering, particularly in conjunction with the suggestion that the identifier is incorrect, is often a result of misconfigurations within the extension’s settings. When you mentioned that you have review the info.plist, could you please clarify what you mean? Ensure that the main app target’s Entitlements file contains the necessary capability, however it seems like the issue is on your info.plist even thought you didn’t provide it on your post. Albert Pascual
  Worldwide Developer Relations.
4w
Reply to Behavior of Bookmark URLs and Files App Recently Deleted – Clarification and Potential Bug
Sharing your bug number regarding this topic which I previously filed. FB21561068 Perfect, thank you. Precondition: Download the attached sample project (TrashedFileURL.zip) in the feedback which I shared with you above and build the TrashedFileURL.app from the project inside the zip folder. I took a look at your sample and the answer is basically, yes, I think there's a problem on our end. More specifically, looking at the three APIs: URLsForDirectory-> This should probably just return NULL, given that there isn't a universally accessible trash target on iOS. URLForDirectory:appropriateForURL:-> I think there's an argument this should have returned /Documents/.Trash/, since we knew the target file. However, it might end up returning NULL as well, as I'm not sure moving the object to that location is necessarily equivalent to trashItemAtURL in the same way it would be on macOS. getRelationship(NSTrashDirectory)-> This is the critical failure, since we specifically returned the wrong
Topic: App & System Services SubTopic: Core OS Tags:
4w
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
755
4w
Reply to Share Issue
Given that the behavior is inconsistent on different device models, I’d suggest that you file a feedback report – If you do so, please share your report ID here. Thanks! Best, —— Ziqiao Chen  Worldwide Developer Relations.
4w
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
7
0
242
4w
Reply to Asset Pack Limit
Hello, @brian_bern! We’re happy to report that the issue is now resolved. If you still can’t upload new asset packs after archiving other asset packs, then please file a new feedback report and reply to this thread with the feedback ID. Let us know if you need anything else. Thanks!
4w
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/Versions/A/AppIntentSchemas but I f
2
0
70
4w
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 Carthage, up
4w
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-4886-A5E3-A
4w