We are unable to process your request

Thanks for your reply. I originally thought those headers were there because I was forwarding requests to an ngrok server over to my local dev server, but I was able to test this in a live env and we do pass requests through another server first. I'm unable to send requests straight to the server because I can't change our underlying system. Also, we always pass requests through another server first and we only have this issue with the Stripe Apple Pay integration. I thought maybe there was a reason why this header was blank, like there was something wrong on Stripe's end. If there's not a real problem then we can just handle the blank header on our side. I'm also realizing that both you and I included the IP address in the HTTP_X_FORWARDED_FOR header in previous comments, but I am unable to edit mine. Are you able to edit or delete past comments so we can remove that IP address?

please go to see the post :Unable to Run Application on Device “dyld: Library not loaded”there is a process to clean all certificates and rebuild all the chain... and it worked for me.

Hi, Same behavior on a Mojave 10.14.6 machine, on a script virtually unchanged since 2019. Last successful notarization on 27th of March, haven't had a batch of builds since; today keeps kicking my shins. Submitted the details under report: FB9079544 (Unable to notarise: Unable to find requested file(s): metadata.xml (1057)). Thanks.

OK, got it. My SKRequestDelegate was being released before the request could be processed. My bad.

Same here, anyone know how to resolve this { responseId: efe442ef-cb6f-4b08-8954-84ec2421b1bd, resultCode: 202000, resultString: Your request could not be processed, userString: Your request could not be processed, creationTimestamp: 2021-06-30T17:05:53Z, userLocale: en_US, requestUrl: https://developer.apple.com/services-enrollment/submitIndividualEnrollment, httpCode: 406 }

I’m not going to be able to help you with this. We don’t support folks killing arbitrary system processes. This is problematic for a variety of reasons, but the big issue here is that the name, location, and behaviour of system processes are all implementation details. If you build a product that relies on such implementation details, you are likely to run into compatibility problems down the line. Which is exactly what’s happened in this case )-: My advice is that you find an alternative way to achieve your ultimate goal. If you’re unable to do so, I recommend that you file an enhancement request for a supported path forward, making sure to explain your requirements and the reasons why the current mechanism don’t work for you. If you do file an ER, 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