We are unable to process your request

My main point was that you were passing a set containing one giant string, instead of the set of many individual strings that you probably intended.I just included the following line because it had a stray comma in it, in your original post, which needed to be removed.But looking at the interface for SKProductsRequest, it will take a regular Swift Set, so you can do this:let productID: Set = [wnp3skips, wnp6skips, wnp##skips..., wnpinfinite, wnpfailsafe] let request = SKProductsRequest(productIdentifiers: productID)(Remember to replace wnp##skips... in my code with the rest of your IAP strings.)

Location services authorization must be obtained before any CoreLocation service is used (which includes iBeacon region monitoring). Without this authorization your app will not receive any location services from the system.If you are expecting your app to be woken up, that means you expect to be using the location services while in the background. That will require an always authorization.Best time to request this authorization is at the point where you actually plan to use location services to perform a task. As requesting authorization may display an alert to the user, if it is not clear to the user that your app is using location services for a useful purpose, the user may deny your request.

Option 3 is possible, and would be the one I can recommend.Through Bluetooth background modes, your app can connect to and listen for a notification from a Bluetooth 4 device (which can be triggered by a button press).When this notification arrives, your app will be activated in the background for a short time for you to react as necessary.Although, this alloted time will be too short to reliably connect to a server at all times, so you will need to implement a viable way to contact your servers reliably at all times.It is important to remember that all background modes require App Review approval before your app can get to the App Store.You can find more info through these links:Core Bluetooth Background Processing for iOS Apps, for interacting with Bluetooth 4 devices: https://developer.apple.com/library/ios/documentation/NetworkingInternetWeb/Conceptual/CoreBluetooth_concepts/CoreBluetoothBackgroundProcessingForIOSApps/PerformingTasksWhileYourAppIsInTheBackground.html#//apple_ref/doc/uid/TP4001325

Option 3 is possible, and would be the one I can recommend.Through Bluetooth background modes, your app can connect to and listen for a notification from a Bluetooth 4 device (which can be triggered by a button press).When this notification arrives, your app will be activated in the background for a short time for you to react as necessary.Although, this alloted time will be too short to reliably connect to a server at all times, so you will need to implement a viable way to contact your servers reliably at all times.It is important to remember that all background modes require App Review approval before your app can get to the App Store.You can find more info through these links:Core Bluetooth Background Processing for iOS Apps, for interacting with Bluetooth 4 devices: https://developer.apple.com/library/ios/documentation/NetworkingInternetWeb/Conceptual/CoreBluetooth_concepts/CoreBluetoothBackgroundProcessingForIOSApps/PerformingTasksWhileYourAppIsInTheBackground.html#//apple_ref/doc/uid/TP4001325

The proper way to implement periodic connect and download data from a BLE peripheral is to give the peripheral the control.The peripheral can periodically notify your app through a characteristic and then a download can ensue.I understand you would want this to work while your app is inactive the background. There is no time based way for your app to wake up and connect to the peripheral. This procedure must be initiated by the peripheral.Gualtier

>I think thumbnails view is the best! it should be back in iOS and in the Mac.I think... = report a bug/feature request 🙂 - bottom right here, and be sure to add your report # to your thread for reference, etc.

I'm not aware of any bugs quite like that open currently. If you have a project that can reproduce this, please file a bug report (bugreport.apple.com) and attach it, and I'll have a look with a debug CoreFoundation. Thanks! 🙂As an aside, within a single process like this, calling synchronize is generally unnecessary; you only need it if you're about to call exit(), or about to notify another process to read preferences.

Hi Atomic,I set Background App refresh to off for everything (to see if that was the issue) no changeI then set Mobile Data to 3g not 4G that had a minimal improving affect to the tune of aprox 10%I have also put the phone into Airplane mode with WIFI active to close out all mobile comms Still no changeI did a full charge and left the phone sat on my desk for three hours and after hour one I was at 97% So I was hopefulAfter Hour two I was down to 83% - still not using the phone on AirplaneAfter Hour three I was at 52% - again after not using the phone.As for mail accounts I have the usual iCloud acc, An IMAP account and an Outlook account,Must admit I havent tried not activating the mail accounts so I may give that a blast.The strange thing is my iPad though after a full charge it held power really well until it got to 45% then it just bombed out real quick, I was using the same app to word process just seemed to drop to 12% in a matter of 45-50 minuets.Hope this helpsCheersMarciPhone 6 128GB No phot