If I launch an app containing a call directory extension, then with earlier betas it would get enabled (in the settings control panel) automatically.However this no longer seems to be the case with 10.3. AFAICT the only way to enable it is for the user to do so manually by the setting control panel.If this is the intended behaviour, then the call directory extension is now a very useless piece of functionality , unless either a) the app can request the user to enable the extension (as it does for things like contacts access, location etc.) or the app can launch the relevant control panel settings in a view controller so the user can enable it. Howeve neither of these is apparently possbile).I know Apple have been reading and responding to some of the call directory extention threads in this forum, if you are reading this, are you able to comment on the situation regarding enablement of the extensions?

CXCallDirectoryExtensionContext only has an API for adding an entry, not for removing one.Therefore apparently the only way to remove a number previously added is to re-add the entire set of entries minus the one you wish to remove i.e if [1,2,3,4,5][,a,b,c,d,e] has previously been added but now its necessary to remove c, then [1,2,4,5],[a,b,d,e] has to be re-added back.However if the total number of entries involved is in the tens of thousands, or even hundreds of thousands, then this seems absurdly inefficient to have to re-add hundreds of thousands just to remove one. But I can't see any other way of doing it. Is there some other way of removing a previously added entry?

If you use CXCallDirectoryExtensionContext.addBlockingEntry() to block a number, then how do you subsequently unblock it?

A previous posting says it was no problem to add one million numbers with a previous beta using this code:var number = 4915148000000 repeat { context.addIdentificationEntry(withNextSequentialPhoneNumber: + + String(number), label: Extension: + + String(number)) number = number + 1 } while number < 4915149000000However I'm finding thats not the case with beta 4. With an iPhone 6S I can get around 30000-50000. The reason I say around is because the number actually varies. I think the iPhone's internal cache isn't being cleared out, so if you run the extension several times you get a pattern like this:add 20,000 -> suceedsadd 30,000 -> suceedsadd 40,000 -> suceedsadd 50,000 -> suceedsadd 60,000 -> failsadd 50,000 -> failsadd 40,000 -> failsetc.It doesn't malk any sense that the second call of 50,000 or 40,000 would fail when the first suceeds, unless there is some internal cache not being cleared. Once its stars failing I find its necessary to reset the phone.Note that in the failure scen

I've got an action extension which I'm invoking via the Phone app's call history share contact action.My code is as follows: for item in self.extensionContext!.inputItems as! [NSExtensionItem] { for provider in item.attachments! as! [NSItemProvider] { if provider.hasItemConformingToTypeIdentifier(kUTTypeContact as String) { provider.loadItem(forTypeIdentifier: kUTTypeContact as String, options: nil, completionHandler: { (contactCoder, error) in OperationQueue.main.addOperation { if error == nil { if let contactCoder = contactCoder { if let theContact = CNContact(coder: contactCoder as! NSCoder)The data type passed to the completion handler in the contactCoder parameter is NSSecureCoding, however XCode will not compile without casting it to an NSCoder on the last line, but when executed this results in a dynamic cast exception.If kUTTypeContact is replaced with kUTTypeVCard then both hasItemConformingToTypeIdentifier and provider.loadItem will still execute, and I was thinking the type of data passed to the co

Action Extensions do not inherit the icon from their containing app unlike the other extensions. And I've been puzzling for weeks trying to figure out how to add one (adding an app icon image set in the extension's assets catalog does not work).Then I found a tutorial (http://code.tutsplus.com/tutorials/ios-8-how-to-build-a-simple-action-extension--cms-22794)The tutorial says As a finishing touch, you can add an icon for the Action extension. In the Project Navigator, select the project and, under targets, select the ReadItAction target. From the General tab in the App Icons and Launch Images section, tap Use Asset Catalog next to the App Icons Source.But an Action Extension DOES NOT have an App Icons and Launch Images section, at least not in XCode v8. So how can the icon be added for an action extension?

My company has two Apple accounts, an iOS developer account and an iOS enterprose account.Previously these had different agents, however after departures/re-organizations within the company we wish to make the same person/account the agent for both account.The previous agent of the Enterprise sucessfully transferred the agent role over to the new agent.However when the current agent for the developer account is trying to do the same they are getting a message saying :The selected candidate is an agent of another team. Please select a different candiate.Why shouldn't the same person be able to be the agent for two accounts? Perhaps there might be some very slight reason behind this logic if the accounts are both of the same type, but they are not, one is enterprise the other is developer.

I've been using the Call Extension call blocking API since it was available in June without problem. However it is no longer working even with the offical 10.0.1 release.To verify it it not my app that has a mistake in it I did this:1) Create a new XCode project template app2) Create a Call Directory Extension Target3) In the extension template code that Xcode generates, change the 14085555555 number in the addBlockingPhoneNumbers method to one of my own number (yes I know they must be registered in order, this number is Seattle area code so its 1206nnnnnnn and hence is in the correct order).4) Run the app, enable the extension, step through the extension code and confirm it is executing without problemMake a call from the blocked number -> the number is NOT blocked.Anybody else had this problem?

I've got 3 iPhone 5, 2 iPhone SE, 2 iPhone 6, an iPhone 6+ and an iPhone 7.I've found that my app which uses a call directory extension won't work on any of the three iPhone 5 devices but there's no problem with it working on the other 6 assorted devices.In case there is some problem with my app, I created a new app with a call extension which was created entirely using the XCode project templates (the Xcode call directory target template creates a lot of boilerplate code which is fully functional and will run and work without further change).I got the same results - the template app also does not run on any of the iPhone 5 but it does run on the other 6 devices.The conclusion from this would appear to be that for some reason call extensions don't work on an iPhone 5, however this is not a correct assumption because I downloaded an app from the app store (Hiya) which uses call extensions onto an iPhone 5 and it ran ok.So it is a mystery to me why both my app and the Xcode template app both do not work on any

I've got an app that uses the Call Directory Extension has has been working fine for several months.I updated a device to 10.3 beta and the app now fails (it was working before the update). Tried it with another device and its the exact same error.The XCode log shows this internal Apple error when getEnabledStatusForExtensionWithIdentifier is called:*** Unable to check enabled status of call extension 1 sqlite3_prepare_v2 for query 'SELECT id, bundle_id, priority, state, state_last_modified FROM Extension WHERE bundle_id = ?' returned 1 errorMessage 'no such column: state_last_modified'The extension is not appearing in the Call Blocking & Identification section of Settings.Anybody else experiencing a similar issue?

With all previous versions of iOS 10.n release and beta, when an app was installed that contained a call directory extension it would appear in the Call Blocking & Identification section of the settings app almost immediatly.But with 10.3 beta 3 it is taking at least 10 seconds before it appears (this is on a fast iPhone 7).Install the app, switch to Call Blocking & Identification, there is nothing there.Wait, wait some more, keep waiting, then it appears.This is too slow. It needs to be visible to the user asap after installation so the user can enable it

When an app which uses a call directory extension gets installed onto a device, then that extension appears in the Call Blocking & Identification section of the Settings app.This is how long it takes to appear there:< 10.3: approx 1 second10.3 beta 2: approx 10 seconds10.3 beta 3: approx 20 seconds10.3 beta 4: approx 30 secondsHow's long is it going to take to appear in beta 5? 40 seconds?it had better go back down again in the final release, its a serious useability issue it taking this long to appear - it looks to the user there is nothing there if they are promted by the app to enable it.

Its surprisingly difficult to find a definitive answer to this. Its not stated if this is the case or not in the Apple documentation and I couldn't find a definite yes/no after searching the internet - most of the material contradicts each other.The Apple documentation states If you do not call the completion handler in time, your app is terminated. But that says nothing about if your app is launched into the background in the first place in order to perform the background fetch.By stating this Apple implies your app must already be in the background in order for performFetchWithCompletionHandler to be called, but they don't specifically say so, and if that is the case then that is opposite of what this book says If the application is not already running in the background when a fetch is scheduled to occur, it will be launched in the background by the operating system and the fetch delegate method called.http://www.techotopia.com/index.php/IOS_7_Multitasking,_Background_Transfer_Service_and_Fetching#An_Overvi

There's a serious problem with XCode 9 where its not possible within a storyboard to make an addition to an IBOutlet collection.In one of my projects I have declarations such as:@IBOutlet var someCollection: [UITableViewCell]!If I try and drag and drop a table view cell to add it to the collection then XCode 9 won't let me - it only displays the Insert Outlet or Outlet connection pop up, it simply refuses to display the Connect Outlet Connection pop up.If I open the same project in XCode 8 there is no problem - it does display the Connect Outlet Connection pop up.Anybody know of a workaround for this which doesn't involved having to revert to XCode 8?

So with IOS 11, sandbox purchases is just totally broken.There's a thread from June first reporting this problem https://forums.developer.apple.com/thread/80560.That was 4 months ago and still the problem persists.I have several devices with iOS 11 installed on them, I also have several existing sandbox test IDs and have created several new ones to try to get things to work.Not one single combination of device with existing id nor new id works. Every time the attempted purchase fails. Nor does the workaround provided in the thread above work.*** 100% failure rate with iOS 11***I still have one device with iOS 10 installed, *every* single combination of purchase with every sandbox id works.***100% success rate with iOS 10 using the exact same app and product ids and apple ids as used when iOS 11 attempts fail ***That tells its own story. Need I say any more, except to ask and plead when will this be fixed?