dsym file

Thanks for those additional answers. [quote='873877022, Retouch, /thread/813562?answerId=873877022#873877022, /profile/Retouch'] I understand it refers to the scenario: “You have an existing flow object …” [/quote] OK. The error you’re getting is NEAppProxyFlowErrorDomain / 1. That’s a bit confusing because the error domain string doesn’t match the error domain identifier. In fact, the identifier is NEAppProxyErrorDomain: print(NEAppProxyErrorDomain) // -> NEAppProxyFlowErrorDomain So, code 1 corresponds to NEAppProxyFlowErrorNotConnected, which is documented to mean: The flow is not fully opened. However, you’re sure that the flow was fully open, so it’s not that simple. I did some digging and it seems that this error is caused by you attempting to write when the write side of the flow is closed. There’s a couple of ways that might happen: If you write to the flow before the open is complete. Or at least I think that’s the case. I wasn’t able to be 100% sure about that, and I declined to research further

[quote='873863022, DTS Engineer, /thread/813853?answerId=873863022#873863022'] may I ask you to file a bug with that project? [/quote] Before you do that, I’d like to clarify what you mean by this: [quote='813853021, OC_s, /thread/813853, /profile/OC_s'] How do I determine the real values? [/quote] What specific information are you looking for here? And what do you plan to do with that information? This matters because Mac Catalyst is returning values that make sense in the iOS-ish environment that’s expected by such apps. It is possible to get ‘real’ values, but the best way to do that depends on your specific setup. For example, the systemName property is uninteresting in a Mac Catalyst app because the real system name is macOS. So you can do this [1]: let systemName: String #if targetEnvironment(macCatalyst) systemName = macOS #else systemName = device.systemName #endif However, that’s just one of these properties. The best path for the other properties varies based your the specific property and

@DTS Engineer Our iOS app receives filenames from a server (e.g., ~TestFile.irfd). We need to extract the filename without extension for display purposes. The original code used: func getFileName(fileNameWithExtension: String) -> String { // Pure string manipulation - correct for filename handling let fileName = URL(fileURLWithPath: fileNameWithExtension).lastPathComponent return fileName } This worked on iOS 18, but broke on iOS 26 when customers started using filenames beginning with ~. We don't actually need a URL or path. We're doing pure string manipulation on a filename to extract components. We used URL(fileURLWithPath:) as a convenient way to get lastPathComponent, but that's semantically wrong for our use case. This will be right suitable approach for our case, let fileName = (fileNameWithExtension as NSString).lastPathComponent This is the right approach because: We have a filename, not a path We need string manipulation, not path resolution NSString.lastPathComponent doesn't perform path resolut

Also CFURL is documented to have different behavior but CFURL and NSURL aren't they 'toll free bridged' so how does that work if you cast a CFURL to a NSURL? So I just did a dumb little test to answer this. I created a CFURLRef and read kCFURLIsHiddenKey and got false (as expected) so it would cache it. Then on another CFURL instance (that points to the same file) I did the same thing (so it was cache the value). After that I set hidden to YES: NSURL *toNSURL = (__bridge NSURL * _Nonnull)cfURL; [toNSURL setResourceValue:@(YES) forKey:NSURLIsHiddenKey error:nil]; Then back to the other instance I cast that one to another NSURL: NSURL *nsCastCopiedVersion = (__bridge NSURL * _Nonnull)aCopiedCFURL; And read isHidden and it is NO. Read aCopiedCFURL hidden and it is also NO. Then dispatch after dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(2 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{ [URLPrinter printCF:aCopiedCFURL]; [URLPrinter printNS:nsCastCopiedVersion]; }); And got: Print copied CF

Hi! This is still a bug in 2026 and I just now got really confused by it. I've filed a feedback about it: FB21767706

Filed a feedback report under FB21767675 (Purchase Intent API does not tigger confirmation dialog to complete the purchase on iOS 26)

Thanks for this, yes, very interesting, may I ask you to file a bug with that project? Well, looks like we only need this part: - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { UIDevice *d=UIDevice.currentDevice; for (NSString *k in @[@name, @systemName, @systemVersion, @model, @localizedModel, @userInterfaceIdiom]) NSLog(@%@ -> %@, k, [d valueForKey:k]); switch (d.userInterfaceIdiom) { case UIUserInterfaceIdiomUnspecified: NSLog(@UIUserInterfaceIdiomUnspecified); break; case UIUserInterfaceIdiomPhone: NSLog(@UIUserInterfaceIdiomPhone); break; case UIUserInterfaceIdiomPad: NSLog(@UIUserInterfaceIdiomPad); break; case UIUserInterfaceIdiomTV: NSLog(@UIUserInterfaceIdiomTV); break; case UIUserInterfaceIdiomCarPlay: NSLog(@UIUserInterfaceIdiomCarPlay); break; case UIUserInterfaceIdiomMac: NSLog(@UIUserInterfaceIdiomMac); break; case UIUserInterfaceIdiomVision: NSLog(@UIUserInterfaceIdiomVision); break; default: NSLog(@Idiot unknown); } exit

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

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

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.

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.