file uri scheme

With card present environments, what's happening there is Apple Pay is sending the DPAN and cryptogram to the terminal, and terminal completes the charge. However, in card not present environments, from a payment processing UX perspective, the user has to see the amount they are confirming for pre-authorization. Otherwise it could lead to fraud cases. You could consider talking to your gateway or bank for Credential On File (COF) if you want to implement something similar to card present environments: You can save the card with a symbolic amount (or zero if the banks allow it) and then use the card you saved for the actual charge. But please beware that Credential On File brings its own set of rules and implementation requirements.

That could be a little problematic to have all gateways in the same domain because as far as I understand, Apple provides the domain verification files per platform integrator, so the gateway that provided you with the verification file is your integrator. And I am not sure how Apple treats multi-integrator platforms. Is it possible for you to register as a merchant, decrypt the payload as a merchant and then send the transaction to gateways for authorization? That might be a better solution.

Thanks. I added a link to this post to the feedback. NSDocument.fileURL is nil for a new document that hasn't been saved – In that case, when you try to terminate your app or close the document window, AppKit shows an alert asking if you'd save the document, and so you should be fine. Yes, but only assuming that the document has been marked as dirty... which is what we're trying to work around. I noticed that there is another issue now: Create a new document. Type a letter. Switch to another app and back again. Type another letter. Quit and restart the app. The document is correctly restored, but when selecting File > Close (or hitting Command-W), it is closed without asking whether I want to save or discard it, and so it probably stays in its autosave directory without the user knowing where it is. This is my current implementation: class Document: NSDocument { private var textStorage: NSTextStorage! private(set) var savedText: String? override func data(ofType typeName: String) throws -> Data

I filed a bug report (FB20465338) but I also want to note some more details here in case this is useful to someone: When navigating back/forward in a WebView or WKWebView, the page suddenly jumps up. The reason appears to be that WebKit automatically adds some padding to the top of the webpage to account for the unsafe nav bar area, but it then forgets to account for this padding when navigating back/forward. The effect is especially pronounced if you swipe back/forward. When swiping you see a static preview of the incoming page, but when you release the swipe, the page suddenly jumps up. As far as I can tell, this has always been an issue, but before iOS 26 it wasn't really a problem because the WebView would usually be flush against a solid nav bar. However, in iOS 26, this bug is problematic because Apple is asking us to flow the web content behind the nav bar; indeed, this is the default behavior of a WebView. There's effectively no good solution in iOS 26 because you basically have two choices:

It will only work if you're building the app using Xcode 26. You also need to add the .icon file to your app. I was able to just drag and drop the file next to me assets bundle and it deployed it to my asset bundle in the next build.

[quote='856112022, Evozi, /thread/73148?answerId=856112022#856112022, /profile/Evozi'] How about iOS 26? [/quote] AFAICT the limits are unchanged on iOS 26. If you’d like to see bigger limits, the best way to get that feedback in front of the folks who have the power to enact change is file it in Feedback Assistant. Make sure include details about what you’re trying to do and why the current limits are negatively affecting your users. Please post your bug number, just for the record. Also, keep in mind that iOS 26 runs on old devices which are significantly more memory constrained than the shiny new hardware you might be using. My daughter may one day have to give up her iPhone SE (2nd generation), and thus accepted the new reality of Face ID, but today is not that day (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hey, Here I am attaching both the requests. This is the CURL request that returns a 410 status with the 'Unregistered' error. (Timestamp: 11:07 AM IST) ~ % curl -v --header authorization: bearer ${AUTHENTICATION_TOKEN} --header apns-topic: com.testcompany.sampletest --header apns-push-type: alert --header apns-priority: 10 --header apns-expiration: 0 --data '{aps:{alert:{title:Test Notification Title,subtitle:Test Notification Sub Title,body:Test Notification Body}}}' --http2 https://api.push.apple.com:443/3/device/devicetoken Host api.push.apple.com:443 was resolved. IPv6: (none) IPv4: 17.188.169.222, 17.188.169.160, 17.188.170.97, 17.188.170.156, 17.188.169.28, 17.188.169.223, 17.188.169.92, 17.188.171.221 Trying 17.188.169.222:443... Connected to api.push.apple.com (17.188.169.222) port 443 ALPN: curl offers h2,http/1.1 (304) (OUT), TLS handshake, Client hello (1): CAfile: /etc/ssl/cert.pem CApath: none (304) (IN), TLS handshake, Server hello (2): (304) (IN), TLS handshake, Unknown (8): (304) (IN), TLS han

Please file a bug report about this issue with 26.1 right away. We would also need diagnostic logs, It would be very helpful if you could please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Location Services for iOS to install a logging profile on your devices. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose for both devices. And attach that to the Feedback report as well. To file a Feedback Report, you can use the Feedback Assistant. Once you have done so, please share the Feedback ID on this thread so I can make sure the team is aware of it. Once the Location team is on the case, they may contact you for further information or specific test cases.

There is a known issue which is being fixed in iOS 26.1 If the issue you are seeing still persists in the latest 26.1 beta, please file a separate bug report explaining in detail the issue you are seeing and how exactly you are specifying the custom sound.

Hello, Could you tell me more about these watchOS targets? My primary curiosity is how they are able to build successfully even during a normal build, if their dependencies do not support watchOS. To more directly address your questions, Localization Export and Import are intended to cover all localizable content in the sources of the entire project or workspace. This way, a single xcloc/XLIFF file can be used for the entire project. Is directly parsing .xcstrings files and generating XLIFF an acceptable alternative, or does this miss important metadata that -exportLocalizations would include? This could work for your use case, but it is not a recommended flow and could miss a lot of things that Export would give you. Also, the xcstrings format is not guaranteed to remain stable from version to version. When you Export with Xcode (GUI or CLI), Xcode does the following: Includes strings from existing .xcstrings, .strings, and .stringsdict files in your project. Extracts localizable s