“We are unable to process your request”

I looked at using requestLocation but as that only performs one request rather than continous requests I was hoping there would be another way as I share the code for both the iPhone and Watch app.I use a distance filter that only gives me locations when I've moved a certain distance which is really convenient so I guess I need to implement a similar setup for the watch, or as suggested above keep location functionality on the phone.

Hi Here is the latest crash logApp launch -> login -> fetch data show data for a second and crash{app_name:OIDAR,app_cohort:2|date=1433912400000&sf=143464&tid=3231324fdde256ebb12259fd91884ff385f8bc040d77173fede1785edaa01bff,app_version:2,slice_uuid:66b2d6ab-d787-3b15-95dc-a3678d6713bd,adam_id:883207563,build_version:23,bundleID:com.oidarapp.oidar,share_with_app_devs:false,is_first_party:false,bug_type:109,os_version:iPhone OS 8.3 (12F70),is_beta:true,name:OIDAR} Incident Identifier: 2C332772-B316-4FBE-9AFE-4CAA0C337F2F Beta Identifier: 87CEC1DE-409A-4204-AD9F-B36D624090BF Hardware Model: iPhone7,1 Process: OIDAR [1829] Path: /private/var/mobile/Containers/Bundle/Application/1528C051-37FB-4F76-9E6C-62ADD1EC3AE1/OIDAR.app/OIDAR Identifier: com.oidarapp.oidar Version: 23 (2) Beta: YES Code Type: ARM-64 (Native) Parent Process: launchd [1] Date/Time: 2015-06-10 13:06:25.053 +0800 Launch Time: 2015-06-10 13:06:04.297 +0800 OS Version: iOS 8.3 (12F70) Report Version: 105 Exception Ty

I'm stuck here on 2009 Xserve's that need to go, but really no options these days. I wish Apple would have kept OSX and OS X Server seperate and then made OS X Server allowed to be installed on PC hardware under VMWare. All of our servers have been on VMWare now for years and now they are trying to push our clients to that as well with zero clients. Little dangerous for me as they are trying to get rid of the Macs in the process, but it woud be nice to be able to use OS X Server on non mac hardware or bring out server grade hardware again. I always wanted a 3U or so Xserve with atleast 8 Drives in it.

I tried to downgrade because i have to send my iphone off to Apple due to a fauty screen, but it fails half way through teh usuaul process. It say the phone failed to restore and then tries to download 8.3 again (even though i've jut told it to instal that a few minutes beofre hand). From previous betas this hasnt been a problem. UPS are due in 1/2 hour to pick up the phone so this is a bit of a problem!Legally speking I fail to see how Apple can void a legal gaurantee for a hardware defect because i put an authorised developer release on via a dev account etc on, but I really dont want them to have to recieve a phone with a dev release on and then refuse it!W

I found my iMac struggling to wake up. I waited, and it eventually did. I found a process, sdmd had eaten all the memory. After a reboot (Which took a while!), it now seems to be fine, and this process hasn't run away with the memory again.I suspect it's some form of indexing daemon that isn't properly optimised yet.

But the link to request an expedited review remains the same and still redirects to the page cannot be found page.

You absolutely have to file enhancement requests and bug reports making your case for the features that you want that iOS doesn't yet support. You probably won't get any direct feedback unless there's difficulty understanding something in your report, but it's still necessary.On the other hand, it's important to remember that Apple applications have both a longer leash (Apple makes the rules) and a shorter leash (Apple's going to be more conservative about most things). The complication with doing a specific task that lasts less than 10 seconds at a specific date and time in the future is one of managing when a dozen different applications all want to do something at the same time. Who goes first? How much time do the have? How does the user tell what's going on? If the foreground application is hogging resources, do you launch late? What happens when you crash in the background?

It's a known bug in 10.10.3. As you've found, the workaround is to set the content-type header directly in the request. If you want to submit an additional bug report, you can say it's a duplicate of #20340623.

Yes.A central focus of Metal is to dramatically reduce the CPU cost of common operations. However, it is still quite possible for wasteful code to blow out the CPU cost and end up running slowly and eating up a bunch of battery life. That is, even though the CPU and GPU can run concurrently, your GPU frames can't cycle any faster than the CPU workload required to encode / enqueue them. Thus, quite a lot of making Metal go fast can be making sure that your CPU workload isn't consuming all your time. For me, the CPU cost is usually around 10% or less of the GPU time in well behaved code. If you are running more than that, then you may need to spend some time finding out why.Most of the time, it comes down to object reuse. It is maybe the key way to improve Metal performance. Much of Metal is designed around the assumption that you will allocate expensive resources (textures, buffers, shaders, queues) up front and then reuse them. As an application writer, this is fairly simple, since you should know in advance

For internal document which will explain the architechture, lifecyle, deployemnt procedures, isn't that the sort of thing that people spend endless hours arguing about in software development classes?I mean, there are standardized data flow diagram methods, software architecture diagram methods, and the like, probably as many different standards as you'd care to find.