I'm attempting to use the new contacts framework, but literally can't get past the first line - adding Contacts as an import fails with the error message Cannot import module being compiled with XCode 7.0 beta 5.I've added Contacts.framework to the Link Binary With Library, but the error message is there regardless of this.

In the olden days when I added a new device id to the provisioning portal I could then go and edit the relvant profiles to include it and then download the profile or pull it down from within Xcode.However now it is no longer possible to directly edit any profiles from within the portal, instead things are managed from within Xcode.However in Xcode 7 (and 7.1 beta) the little circular button to refresh the profiles has gone, when viewing the list of profiles the actions column in blank, and the download all profiles button doesn't do anything if the profiles are already downloaded.So the question is, if a new device id gets added to the provisioning portal, how do you get it inside a profile and that updated profile installed on the Mac/ XCode?

I've found that if there is more than one call extensions installed, each of which lists the same telephone number(s), then the one which is installed first is the one the OS chooses which labels to display (even if the extension which is installed second has its reloadExtension invoked by the containing app).Its possible to determine if an extension is enabled or disabled by using CXCallDirectoryManager.sharedInstance.getEnabledStatusForExtension(withIdentifier:Where the identifier is of the form com.company.ContainingApp.CallExtension.Is there any way of finding out what the identifiers of any other extensions installed are in order to determine their enabled status? I doubt it, but thought I might as well ask just in case.

I can successfully get a service extension to work (for both a local notification and a push notification) but I'm not able to get a UI content extension to work.I created one using the XCode template and haven't editied it beyond that.Then in my container app I'm doing the following to register a category: let customUICategory = UNNotificationCategory.init(identifier: myNotificationCategory, actions: [], minimalActions: [], intentIdentifiers: []) UNUserNotificationCenter.current().setNotificationCategories([customUICategory])And in the push payload added: category: myNotificationCategoryThe XCode template automatically added the UNNotifictionExtensionCategory key to the extension Info.plist, which has the name myNotificationCategory.The push is sucessfully delivered to the device and displayed and a service extension is run but the content extension.Anybody been playing around with a content extension and managed to get it to work?

If an app is running the background and received background pushes, then if the device is restarted (without the user having terminated the app) then background pushes no longer work.I was under the impression background pushes would survive a reboot provided the user didn't terminate the app. But apparently not, unless this feature did work and is no longer doing so in iOS 10.Can anybody clarify?

Will it be possible to submit an app built only for iOS 10 to the app store so it is ready for when iOS 10 is fully publicly released? I.e. submit it for app store approval a few days or a week before the anticipated relese date of iOS 10?Its not possible to submit an app built with an XCode beta, so historically how is the beta status of XCode tied to relese data of IOS? In other words, will XCode 8 remain in beta until the extact time iOS 10 becomes none beta? Or could XCode 8 come out of beta status before iOS 10 does?

WIth beta 2 I can still add phone numbers via the phone extenison however it is only those added at app installation time. I can't change this as calls toCXCallDirectoryManager.sharedInstance.reloadExtension() (and CXCallDirectoryManager.sharedInstance.getEnabledStatusForExtension()) are both resulting in an error.In Beta 10.1 I had these working, now in 10.2 they no longer are.Anybody else have the same problem, or a solution?

I have notification service extension and I can get it to execute if the payload is like this (in php)$payload = json_encode([ 'aps' => [ 'alert' => Hello, 'sound' => 'default', 'mutable-content' => $isContentMutatable, ] ]);But not if it is something like this:$payload = json_encode([ 'aps' => [ 'alert' => ['title' => 'Game Request'], 'sound' => 'default', 'mutable-content' => $isContentMutatable, ] ]);Anybody been able to get it to be called when the alert is anything other than just a string?

In the WWDC 16 Advanced Notification talk an example of writing a service extension is provided with the service adding an attachment to the notification (06:08 to 06:46).The presenter then says After I've done this, this is my notification and shows what the notification looks like (06:53) and the notification is shown as displayed with a large picture taking up about 1/2 the device screen, and a couple of action buttons beneath it. However it seems impossible to actually get a notification to appear like this using a service extension- if I try and add a picture as an attachement in a service extension the result is that the picture appears as a small icon on the right hand side of the notifiation.The only way I can get an extension to appear like in the presentation is to use a UI extension and in addtion the user has to explicity expand the notifcation from its compact form to its expanded form.But this is not what the presenter says, he is using a service extension and he says its displayed as a large ex

I wrote a notification content extension which with 10.1 was working perfectly and reliably - it was getting called 100% of the time, as it should, and eveything was great and working as it should.But now with 10.2 I just cannot get the bugger to work at all - the extension just isn't being called by the OS (actually it was called once out of about 30 attempts and on that one occasion the UNNotificationExtensionDefaultContentHidden YES flag was ignored, which it didn't use to be with 10.1)Anybody else having problem with content extensions with 10.2, but if not is there some trick or tweak or change you applied to get them to work?

If I add an image to a notification then when its displayed as an icon in the notification compact state what is shown is just the the center of the image and not all of the image.So I tried passing clipping options as below: let clipping = CGRect(x: 0, y: 0, width: 1.0, height: 1.0) let options: Dictionary<String, AnyObject> = [UNNotificationAttachmentOptionsThumbnailClippingRectKey: clipping.dictionaryRepresentation] let icon = try UNNotificationAttachment(identifier: icon, url: url, options: options)But it made no difference.

I noticed if I tried to do something in the application (in userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: () -> Swift.Void) after the user clicks on a notifiation action that it was taking about 10 seconds before it would be performed.So I added some logging to see what was going on and there is a 10 second gap between userNotificationCenter:didReceive getting called and applicationDidBecomeActive being called.I've not used notification actions prior to iOS 10, is this something that has always happened or is it likley to be a bug with the beta?

Yesterday I downlaoded XCode 8 Beta 3, overwriting beta 2. However I want to re-install beta-2 could couldn't find it anywhere.Are the previous betas still available somewhere?

If I send a push to a device when the lock screen which has gone to sleep, then the push is waking the device up when it arrives but the push isn't being displayed on the lock screen (it would be beta 10.1).

This has been driving me nuts, the following code sucessfully runs when a call directory extenion is loaded via CXCallDirectoryManager.sharedInstance.reloadExtension() let (phoneNumbers, labels) = ([+12061110002, +12061110003, +12061110004], [A, B, C]) for (phoneNumber, label) in zip(phoneNumbers, labels) { context.addIdentificationEntry(withNextSequentialPhoneNumber: phoneNumber, label: label) } context.completeRequest()But this code fails: let (phoneNumbers, labels) = ([+12065549472, +12061110003, +12061110004], [A, B, C]) for (phoneNumber, label) in zip(phoneNumbers, labels) { context.addIdentificationEntry(withNextSequentialPhoneNumber: phoneNumber, label: label) } context.completeRequest()The *only* difference is in the succesful case the first number is +12061110002 and in the unsucessful case it is +12065549472.It fails with error code 4 on beta 10.2 but error code 3 on beta 10.3. Its 100% reproducable, I have two phones, the first code suceedss %100 of the time its run, the seconds code fails %100 of