Search results for

We are unable to process your request

69,640 results found

Post

Replies

Boosts

Views

Activity

Reply to Nested Assync URL datatask
So I try to insert dispatch_async(dispatch_get_main_queue()) and doesn't work too. Define “doesn’t work” in this context. Are you saying that it doesn’t get you to the main thread? Or that it doesn’t help you serialise your posts.Is there a way for make post sync post?That is not recommend and, anyway, shouldn’t be necessary.In my case the problem is that I need to do 2 posts, the second one I will do onlyt if the first was successfull.A simple structure for this would be:session.dataTask(… first POST request …) { if let error = error { … dispatch to main thread and post the error … } else { … process server result … if unsuccessful { … dispatch to main thread and post the error … } else { session.dataTask(… second POST request …) { if let error = error { … dispatch to main thread and post the error … } else { … process server result … if unsuccessful { … dispatch to main thread and post the error … } else { … dispatch to main thread and post success … } }
Jan ’17
Reply to EADemo update
We are developing IOS App where we can send the request to(Head unit/Car audio Receiver which my app is connected using External Accessories Framework ) Via Bluetooth and wait for response from (Head Unit /Car audio Receiver ),Based on response again we will trigger other request.In same Fashion ,Head Unit Will trigger request to IOS app and IOS app will process the request than It sends the Acknowledgement,After that IOS app will send the response by generating some command(Synchronised method) as response Which should be managed by Thread .Our problem comes into the picture when we are trying to read incoming request based on that , sending Acknowledgement.Here thread should called automatically saying that ACK IS OK. we will release Thread after that it will send other command as response vice -versa.That is what we are unable to do it Because here we need to implement semaphore, deadlock and timer.
May ’16
Reply to Cancel subscription not working in TestFlight
I am unable to cancel my sandbox subscription: Your request is temporarily unable to be processed. The monthly subscription is renewing on a daily basis, which is odd because typically it is faster. Here is a possible clue: When I did the in app purchase, typically, I get a second confirmation box saying You're all set. However, this last time I did not. I then tried to subscribe again, and it said I was already subscribed. I then went to my database, and noticed that the purchase ID was different than the one I can obtain from the store API. It's been days and the subscription just keeps renewing. I tried to cancel in app, and online (the subscription shows, but cancel button does nothing online either). At this point, I can no longer test subscriptions.
Topic: App & System Services SubTopic: StoreKit Tags:
Dec ’24
Reply to Debugger not starting
did not help me . I still see{NSLocalizedDescription=Unable to bootstrap process with bundleID <bundle id > BKSProcessExitReason=0, NSLocalizedFailureReason=Failed to start job, NSUnderlyingError=0x2869d9ec0 {Error Domain=NSPOSIXErrorDomain Code=3 No such process UserInfo={NSLocalizedFailureReason=The process failed to exec, NSLocalizedRecoverySuggestion=Consult /var/log/com.apple.xpc.launchd/launchd.log for more information, NSLocalizedDescription=Unable to get valid task name port right for pid 13153}}, BSErrorCodeDescription=bootstrap-failed}
Oct ’18
Unable to notarise components because upload fails (Unable to find requested file(s): metadata.xml (1057))
Hi. In the latest days the notarization of some components (dmg, apps, etc) is failing randomly because the upload is failing. The error reported is: error 01-Apr-2021 11:43:16 [2021-04-01 11:43:15 PDT] main DBG-X: parameter iTMSTransporterMode = upload I'm 99.9% sure this is an issue in the Apple notarization service because if the same component is uploaded again the notarization is success( Sometimes it is necessary to try 3-4 times to actually upload the file) This issue is happening in the latest week. Can you please confirm if something is not working properly in the notarisation service? Attached Trace log - https://developer.apple.com/forums/content/attachment/612f94d3-f1c5-49fc-a4cd-6bde78b8101d is a trace log with the error
1
0
686
Apr ’21
I/O exception (java.net.SocketException) caught when processing request to {s}-&gt;https://appleid.apple.com:443: Connection reset
Hi , We are implementing apple-sign-in. Made all the code changes mentioned in apple rest implementation document. Now when we moved our code changes to staging environment we facing error I/O exception (java.net.SocketException) caught when processing request to {s}->https://appleid.apple.com:443: Connection reset we changed all our fire wall settings and when we telent appleid.apple.com 443 we make connection. But when we try telnet appleid.appple.com still we are not able to establish connection. Please some one suggest what is wrong here ?
1
0
2.0k
Jun ’20
Unable to Add Non-Standard Headers Using Declarative Net Request Rule (DNR) in Safari
We’re encountering an issue when trying to add non-standard headers to outgoing requests using Declarative Net Request (DNR) rules in our Safari Web Extension. Tested on macOS 15.4 with Safari 18.4. Specifically, when attempting to add a custom header such as X-Custom-Header using a DNR rule, the header does not appear in the request. We are able to add standard headers like Authorization and Cookie to the request successfully using the same method. This behavior suggests that Safari may be filtering or blocking non-standard headers when set via DNR rules, unlike other browsers. In Chrome and Firefox, the same rule adds the X-Custom-Header header without any issue. We are looking for assistance in fixing these issues and having our Safari Extension function the same as it does in Firefox and Chrome.
2
0
108
Apr ’25