We are unable to process your request

> 1) I would like to monitor the telephony state of the device in order> to be able to reject incoming VoIP call when the user is already> talking on a telephony call.That should be feasible. When your app resumes in order to process the ring indication (that it got via the old VoIP API or via the silent push you get from PushKit), create and start a new instance of CTCallCenter. If that shows that the user is on a call, don't post a ring indication to the user but rather communicate the busy state back to your VoIP infrastructure.> 2) I would like to reject an incoming telephony call (with a busy> tone) if the user is already talking on a VoIP call.That's not possible on the current system. CT calls always take precedence over VoIP calls. If you'd like to see that change in the future, I encourage you to file a bug describing your requirements.<https://developer.apple.com/bug-reporting/>Please post your bug number, just for the record.Share and Enjoy--Quinn The Eskimo!Apple Deve

I've seen reports of this in the past but never been able to nail down the circumstances under which it happens. I'd like to dig into this but that's not something I can do in the context of DevForums. If you'd like to open a DTS tech support incident, we can pick things up there.<https://developer.apple.com/support/technical/submit/>Alternatively, if you just want to work around this and then move on, you can run the request asynchronously and use an NSTimer to enforce whatever timeout you require.Share and Enjoy--Quinn The Eskimo!Apple Developer Relations, Developer Technical Support, Core OS/Hardware

Trace Follows:Anonymous UUID: 0A2A4A75-1866-A4AD-2B2C-E694BCFF5139 Thu Jun 18 10:28:21 2015 *** Panic Report *** panic(cpu 0 caller 0xffffff800ce17cc2): Kernel trap at 0xffffff800d311a93, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x0000000000270027, CR3: 0x000000016070f0bc, CR4: 0x00000000001627e0 RAX: 0xffffff7f8f2ef1a0, RBX: 0xffffff8018036f01, RCX: 0x0000000000800003, RDX: 0x0000000000270028 RSP: 0xffffff801430b968, RBP: 0xffffff801430b990, RSI: 0xffffff801430b9b0, RDI: 0x0000000000270027 R8: 0x0000000000000010, R9: 0xffffff801789c240, R10: 0x0000000000270028, R11: 0x0000000000000002 R12: 0x0000000000270027, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffff8018036f00 RFL: 0x0000000000010246, RIP: 0xffffff800d311a93, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0x0000000000270027, Error code: 0x0000000000000000, Fault CPU: 0x0 Backtrace (CPU 0), Frame : Return Address 0xffffff801430b610 : 0xffffff800cd2bda1 0xffffff801430b690 : 0xffffff800ce17cc2 0xffffff801430b

To the best of my knowledge, the location services don't directly support that.You can use the continuous tracking option at the cost of high battery usage, or use the option to watch for significant changes in location.Neither operates on a specific time frequency.You can simulate time intervals by using tracking results that reflect the time interval you want.It may also be possible to use a timer and request additional background time, but that may or may not really work. Since iOS 7 that only gives you 2 minutes of background time, previously it was 11 minutes.I would imagine the logic was that it was more important to know when changes in location happened than to always get location data at a specific time.The continuous location feature is meant to be used for apps that give directions for travel, with the sigificant distance being used where high precision isn't important.

If you're going to ask for help with error messages, it would be helpful if you can post the actual error message too. Anyway, try:var request: SKProductsRequest = SKProductsRequest(productIdentifiers: Set<NSObject>)func paymentQueue (queue: SKPaymentQueue!, removedTransactions transactions: [AnyObject]!) {You can look this sort of thing up yourself, using the the documentation in Xcode or at the Apple developer web site: just search for the class/protocol, and look for the method in the class/protocol-specific document. The syntax is right there.

Yep, you're right. I didn't pay attention to the first half of the line.Given that it's 'productID' rather than 'productIDs', perhaps what's really wanted is:var request: SKProductsRequest = SKProductsRequest(productIdentifiers: [productID])leaving it to the compiler to construct a Set from the array literal. But we'd really need to see the error message.