“file uri scheme”

Thank you for the thread attached in your response. The issue faced above internal to the Salesforce B2C Commerce Business manager configuration. We are working for a US based site where 3DS is optional for merchants. Hence we did not enable it in our Business Manager portal. Later, we found that 3DS is mandatory for Apple Pay to work. Below is the documentation shared by Salesforce with us. https://developer.apple.com/documentation/applepayontheweb/applepaypaymentrequest/merchantcapabilities This information is neither logged in the browser console nor in the server side logs as there was no authorization event being triggered from applepay.js file hosted on Salesforce B2C Commerce instance. This has become a grey area for us to reach out both Apple and Salesforce. After enabling 3DS, we are seeing the authorization event triggered. Hope this answer helps for others who face similar issue on Apple Pay on Salesforce B2C Commerce aka Salesforce Commerce Cloud (SFCC) formerly known as Demandware.

[quote='880351022, KayleeSC, /thread/791352?answerId=880351022#880351022, /profile/KayleeSC'] Omg it was the / at the end. [/quote] Well, blat! [quote='880351022, KayleeSC, /thread/791352?answerId=880351022#880351022, /profile/KayleeSC'] I’m gonna send this to the testers and see if that’s it. [/quote] Cool. If that does turn out to be the problem, I’d appreciate you filing a bug about it. The system should either tolerate this or vend a more helpful error. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi @Ziqiao Chen and everyone, Thank you for the follow-up. You were right to push for more precise testing — it led me to discover an issue with my original test setup and reach a much clearer understanding of the problem. == Correction: Original Test Setup == My initial frontmost test had a build configuration error: the test build still had an active HKWorkoutSession running in the background. This means the results I would have reported (~10 minutes before termination) did not reflect pure frontmost app state behavior. I've since corrected this and re-tested with precise instrumentation. == Hardware & Software == Apple Watch Series 8 (45mm) — not Series 4 watchOS 11.6.1 (latest stable) Build: Debug, standalone watch app Xcode debugger disconnected before all tests (to avoid priority elevation) == Methodology == I added a 30-second heartbeat timer that logs: Sequential counter and elapsed seconds Current heart rate value and time since last HR sample (hr_age_sec) App lifecycle transitions (ScenePhase ch

[quote='880412022, hasii2021, /thread/818406?answerId=880412022#880412022, /profile/hasii2021'] I put them [in FB22267132] but not sure if this is correct [/quote] That’s cool. When I open the system log snapshot you included (system_logs.logarchive) I see this: type: default time: 2026-03-17 21:32:51.951555 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: UNIX error exception: 2 type: default time: 2026-03-17 21:32:51.951587 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67068 type: default time: 2026-03-17 21:32:51.951603 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67071 type: default time: 2026-03-17 21:32:51.951615 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67071 This seems like an understandable error cascade: The first error, 2, is ENOENT, which is an error commonly returned by the BSD su

Yes, both are signed Executable=/Users/alexf/Library/Developer/Xcode/DerivedData/Passthrough-fmtxodvbsknmqegwvscnzsczlopk/Build/Products/Debug/PassthroughAppEx.appex/Contents/MacOS/PassthroughAppEx Identifier=com.example.apple-samplecode.PassthroughXXXXXXXX.AppEx Format=bundle with Mach-O thin (arm64) CodeDirectory v=20400 size=476 flags=0x0(none) hashes=3+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=9abcde7d8b79d23164600c46c55cdace7136690a CandidateCDHashFull sha256=9abcde7d8b79d23164600c46c55cdace7136690aecb06f89082b53853a045b76 Hash choices=sha256 CMSDigest=9abcde7d8b79d23164600c46c55cdace7136690aecb06f89082b53853a045b76 CMSDigestType=2 CDHash=9abcde7d8b79d23164600c46c55cdace7136690a Signature size=4781 Authority=XXXXXXXXXXXXX Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA Signed Time=17 Mar 2026 at 15:00:17 Info.plist entries=21 TeamIdentifier=XXXXXXXX Sealed Resources version=2 rules=13 files=3 Internal requirements count=1 si

@DTS Engineer I have created fresh virtual machine with latest macOS, installed latest Xcode there and check. Behavior is still broken (check video below). https://drive.google.com/file/d/1THJ-o_4htaP2FvH8w4nt8IsbIsNefgZk/view?usp=sharing As you requested, I've also collected sysdiagnose: https://drive.google.com/file/d/1xv11WVYlVjCEVmggr37cETbqd-5w8Yyd/view?usp=sharing

[quote='880307022, SurferDog, /thread/818415?answerId=880307022#880307022, /profile/SurferDog'] We kind of expect the permissions to disappear when installing an update [/quote] I don’t know why you have that expectation. If both the old and new versions of the code are signed in the same way, the system should maintain the privilege across the update. TN3127 Inside Code Signing: Requirements talks about the mechanism used to implement that. [quote='880307022, SurferDog, /thread/818415?answerId=880307022#880307022, /profile/SurferDog'] I have filed a bug report: FB22261705 [/quote] Thanks! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880390022, Abel_Kefan, /thread/819088?answerId=880390022#880390022, /profile/Abel_Kefan'] I realized that I hadn't added the Hotspot Configuration Entitlement [/quote] Oh, hey, would ya look at that. I can reproduce this myself using NEHotspotConfiguration Sample. If I remove the Hotspot capability I get error 8 when attempting to add a configuration. [quote='880390022, Abel_Kefan, /thread/819088?answerId=880390022#880390022, /profile/Abel_Kefan'] I still think it would be better if the error message [provider] a clearer hint to developers [/quote] Agreed. Please file a bug requesting that and then post the bug number here. And now I’m off to update Understanding NEHotspotConfigurationErrorInternal (-: Thanks for sharing this titbit! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The PPQ outage from last week [1] was a very specific thing and it’s definitely not related to whatever issue you’re hitting now. [quote='819180021, KW-P, /thread/819180, /profile/KW-P'] Ping still fails [/quote] Testing with ping isn’t helpful in this case; AFAICT ppq.apple.com never responds to pings. Consider: % ping ppq.apple.com PING use1-ppq-ext-prod.sbz.apple.com (17.33.200.235): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 ^C --- use1-ppq-ext-prod.sbz.apple.com ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss % curl -I http://ppq.apple.com HTTP/1.1 301 Moved Permanently … Location: https://ppq-ext.v.aaplimg.com/ If you want to try out the redirect link, you have disable the client’s trust evaluation on the server: % curl -I https://ppq-ext.v.aaplimg.com/ curl: (60) SSL: no alternative certificate subject name matches target host name 'ppq-ext.v.aaplimg.com' … % curl -I --insecure https://ppq-ext.v.aaplimg.com/ HTTP/2 404 … Of course, that

I’ve not heard of widespread problems with iCloud Private Relay on the iOS 26.4 betas, but that doesn’t mean that this problem isn’t real. My general advice on this front is that you file a bug. Or, in this case, encourage your user to file a bug. They can do that using Feedback Assistant. Ideally they’d do that immediately on seeing the problem, so that the sysdiagnose log attached by Feedback Assistant captures the issue in progress. If they do this, ask them to pass the bug number along and then post it here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have the log files ready. Can you point me to where to file this bug report I put them here but not sure if this is correct https://feedbackassistant.apple.com/feedback/22267132

Hi and thank you for confirmation for this issue. I've filed a bug on this already (r.172771068), but I'd appreciate your filing your own bug and posting the bug number back here. I have created a Feedback Assistant for this: https://feedbackassistant.apple.com/feedback/22266931 Also created a Code-Level Support case, with the same title as with Feedback Assistant but it seems to be private. Please inform if I may have missed anything. Once again, thank you for support.

Have you filed a bug on this and, if so, what is the bug number? Not yet, but I do have another thread where I describe the same problem in regards to .DS_Store: https://developer.apple.com/forums/thread/819041 I will post the bug number (most likely there) when I carve out a little time for it. Currently if copyfile fails and errno is not set my code falls back to a kind of 'Unknown Error' which I hate but if the user is counting on my app to perform the copy it's kind of a gamble if the operation doesn't succeed to just hope not critical data was lost. A big part of this is that xattrs aren't actually safe“— the system doesn't have a documented system for defining how they should be handled, and app/copy engine/file format support for them is inconsistent, so storing critical data in them can end up being a good way to lose critical data. Importantly, that kind of data loss isn't really a bug in the same way other kinds of data loss would be. The general point of xattrs is to allow the att

I'm experiencing this issue. Copy file works locally for these files but fails when coming from a NAS. So, the first question here is what these files are and how they got onto that NAS. More specifically, there are basically only three reasons a file would have a resource fork today: It's really, really old. Apps were discouraged from using the resource fork from the very first release of macOS X and the Resource Manager (the only API that allowed access to it) was deprecated in macOS 10.8. Files that are intentionally using it should not be common. It's actually a compressed file. I described that case above, but the key point is that compressed files should never be leaking off of our volumes. Something else (weird) is going on which I'd love to understand. The most likely explanation here is #2, however, making that happen means something didn't work properly, which is what you should identify and correct. Works from Finder in both cases, as p