Search results for

We are unable to process your request

69,717 results found

Post

Replies

Boosts

Views

Activity

Reply to How to prevent that our XPC service is getting contantly preempted?
The only solution we found was the same one that also jdv85 shared on StackOverflow. When the app is calling a method of the XPC service for processing, the priority of that XPC service is raised so that the request can quickly be performed as the main app may have to wait for the result of that call. Once processing is over, which is indicated by calling the callback block of the request, the priority level will drop again after a while. By never answering the request, the system believes that the XPC service is still processing it and that way the priority stays up. This also keeps sudden termination disabled automatically for the XPC service as the system will not terminate an XPC process while it believes it is still actively processing data, so we don't need to disable it manually anymore. While this solution works, it's still just a workaround that may break one day in the future, e.g. when Apple decides that there is a time limit f
Mar ’22
Reply to Yet Another Notarization Process Strangeness
This could be the case you're describing precisely in the post you linked to.But I still see 2 issues with having the notarization process requiring changes to the Apple Developer Program License Agreement being accepted:- from what I observed, it was still possible to codesign things. So why should the notarization process be impacted? (N.B. This is not a request to break the codesigning requests too).- changes to the Apple Developer Program License Agreement can not be anticipated by 3rd party developers. So, blocking the notarization process (until the changes are accepted) will block/break automatic processes that make notarization requests. Without reasonable prior notice.
Topic: Code Signing SubTopic: General Tags:
Jan ’20
Reply to Ordering of Transparent Proxy Providers
Our currently sitituation is that when our product is NETransparentProxyProvider Two and another vendor is NETransparentProxyProvider One, we are unable to identify the originating process of the flow content. We curerntly use the flow.metadata to identify the originating process as a browser. However, we do not have that ability being NETransparentProxyProvider Two as flow.metadata reflects process information of NETransparentProxyProvider One. Is there anyway of being NETransparentProxyProvider Two and knowing the originating process information that was intercepted by NETransparentProxyProvider One?
Apr ’21
Network request queue
I want to create a network task queue that will persist to disk so that if the app crashed or was shut down during processing the requests I could restart the app and continue processing the outstanding requests. I'm considering saving the network details to a db table or serializing an object to disk and then using NSOperations to process them.I could restore the objects on startup or read the table to recreate the tasks. Does anyone have any good advice or suggestions for this approach?
1
0
964
May ’17
Reply to iOS 18.2 ImageIO Crash
I sent a feedback with complete crash stack information, I am unable to reproduce this issue, through analysis it should occur when the user is playing a GIF, and we use CGImageSourceCreateImageAtIndex to process it. Feedback
Topic: UI Frameworks SubTopic: UIKit Tags:
Dec ’24
Unable to Add review
Hello guys. I am getting the error below when I try to add my app for review Unable to Add for Review The items below are required to start the review process: There are still screenshot uploads in progress. I keep deleting and adding the screenshots back but I still get this issue. What could be going on and are there any fixes?
1
0
709
Jun ’23
lldb fails to launch process: "Not allowed to attach to process"
Xcode 12.4 on Big Sur, a very basic attempt to launch and debug a process. Little-Net:host-osx minfrin$ lldb ./tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing (lldb) target create ./tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing Current executable set to '/Users/minfrin/src/redwax/open-eid/chrome-token-signing-trunk/host-osx/tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing' (x86_64). (lldb) process launch -i cert.native error: process exited with status -1 (attach failed (Not allowed to attach to process. Look in the console messages (Console.app), near the debugserver entries when the attached failed. The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.)) Why would lldb, running as my local user, be unable
6
0
9.8k
Mar ’21