Hi, yes I'll file a feedback report. The documentation for the new Contact Provider Extension (https://developer.apple.com/documentation/ContactProvider) talks about the app managing its own contacts. If an app were to create a contact for a number (as opposed to the user creating one) would that override the blocking action of a CallKit extension too? (I'd try it out but there is as yet no documentation on how an app can create an app managed contact)

@Gualtier Malde if the token changes, lets say due to the user backing up then restoring, but the user doesn't launch the app, then the app now has a new token but as it hasn't run it won't have the chance to inform the server there is a new token, hence all the pushes will fail. Is there any solution for such situations?

@Gualtier Malde "The only available solution at this time is to reboot the device to clear the problem state." Would deleting and re-installing the app also reset the problem?

I've seen the same thing - RBSRequestErrorDomain code 5. https://developer.apple.com/forums/thread/739274. Since reporting that I haven't been able to capture logs myself, but I've had quite a lot of customers reporting pushes not being displayed unless they restart their phone. So it could be quite widespread.

Thank you for the explanation. Yes, being able to create a debuggable binary would be useful because I'm running a React Native app, and how it behaves, especially on launch/startup is different as when running via Xcode the RN javascript bundle resides on the Mac, but gets copied to the phone during installation from an archive, and this makes a big difference when trying to debug bugs occurring at start up, and examine times on app launch etc.

@jlilest could you describe further what you mean?

@Developer Tools Engineer Is there a way within Instruments to filter the logging by a string? For example suppose my app logs as "X:A:nnn" and an app extension logs as "X:B:mmm", is there a way to filter the logs so it displays any log line containing "X:"?

Thanks for the reply. The issue I'm facing when doing this is that the old logs scroll out at the top of the window even though the window content isn't filling up, i.e. suppose the app runs and logs to the window, then the app pauses for a few seconds and doesn't do anything to generate new logs, then the previous logging scrolls out at the top until an empty log window is all that remains, then its not possible to scroll up to view them, they're gone. I'll give Instruments a try.

Exactly, unfortunately, already experienced that several times in the past.

Instead of saying probably. Find out for certain. Step to that line in the debugger, then step over it, or add logging lines before and after.

@eskimo And is there anything one can do if the app being tested needs connectivity i.e. its making http calls? You can't disabled Wifi in this case (if the phone doesn't have cellular connectivity)

Are you sure you only have one in the application Folder? If within the storage manager thingy if you click on Xcode Universal and then Xcode (V220004) then at the very bottom of the table it shows you the location of what you click on i.e. if might show Machintosh HD > Application > Xcode for one and something else for the other. There is also a Show in Finder button that will open the folder and highlight the selected app

The iPhone OS could do that, the iPhone OS can do anything it wants. But an app cannot. Apple put lots of restrictions on what an app can do, fundamental to that is an app runs in its own little world and has no knowledge nor can interact nor interfere with other apps or the iPhone's general behavior.

I don't really understand what you are asking. There's no ability to search the numbers that are registered within the call extension, but as it would have been your app that added them in the first place you would know what you added. The call extension is only for use with blocking/identifying inbound calls. Your understanding of it sounds a bit confused based on your questions

NO - this isn't a solution, if the code signing entitlements are removed then so too does the shared group, and then the extension won't run - the OS logs "Event (1) dropped for client (com.company.experiments) failed because the app and extension do not share any application groups."