“We are unable to process your request”

@DTS Engineer When I enable and disable it, I do receive the startFilter and stopFilter messages, but I no longer receive the handleNewFlow message. As soon as I receive the stopFilter message, the network returns to normal. By the way, let loNetworkRules4 = NENetworkRule( remoteNetwork: NWHostEndpoint(hostname: 127.0.0.1, port: 0), remotePrefix: 0, localNetwork: NWHostEndpoint(hostname: 127.0.0.1, port: 0), localPrefix: 0, protocol: .any, direction: .any ) A rule like this has also caused complete network outages on many versions of the system. Speaking of which, I urgently need to find a solution. So, I have two requests: When this issue occurs, how can I collect system logs to help us pinpoint the specific problem (it could be a system issue or an issue with our extension)? Is there a way to quickly reset the network? You mentioned earlier that there is a process similar to launchd responsible for the entire lifecycle of the system extension. Can I kill this process to achieve a

Hi @siddakumar, More information is needed to investigate this issue. Please carefully review the resources in the post below: Gathering Required Information for Troubleshooting Apple Pay on the Web Merchant Issues https://developer.apple.com/forums/thread/762994 If, after reviewing the TNs, you are unable to resolve your payment failures, please follow the steps in the post above to create a report via Feedback Assistant. Once submitted, please reply here with your Feedback ID so I may investigate your device logs, and escalate to the Apple Pay Server engineers directly, if needed. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Man, there is so much history here... I tried setting the creation date to: 1946-02-14 08:34:56 +0000 right after creating the folder. But it doesn't have the desired effect. Maybe I didn't convert the date correctly? SO, I had a bit of loose time today, so I threw together this test code: // // main.m // create_time_check // // Created by Kevin Elliott on 3/16/26. // #import int main(int argc, const char * argv[]) { @autoreleasepool { NSURL* url = [NSURL fileURLWithPath: @/Volumes/HomeBase/MassiveTestBed/MassiveTestDirOut/TestDir]; NSDate* date = NULL; NSError* err = NULL; if([url getResourceValue: &date forKey: NSURLCreationDateKey error: &err]) { NSLog(@%@, date.debugDescription); } // Jan 24, 1984, the day the mac was announced... const CFAbsoluteTime kAbsoluteTimeMagicBusyCreationDate = -534528000.0; NSDate* magicDate = (NSDate*) CFBridgingRelease(CFDateCreate(kCFAllocatorDefault, kAbsoluteTimeMagicBusyCreationDate)); NSLog(@File is Busy: %d, [magicDate isEqualToDate: date]); NSURL* targetURL =

Is your project available somewhere where we could look at it with the right link? If it's not in a public place, but you're willing to share it with us privately, please open a code-level support request and we can send you instructions on how to share a copy with us to take a look. — Ed Ford,  DTS Engineer

Same here. Over 5 weeks now. @Tomato , I can't see why calling would fuel delays. That'd be extremely unethical. The reason we are calling is because we don't have any other means of getting answers. We are completely left in the dark in a process that's core to our businesses

Hi @DTS Engineer , I am also facing this weird issue I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info. Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the Generate dSYM phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue persists reg