isSIMInserted is broken and doesn't work with beta 1 and beta 2, you need to use beta 3. And the subscribers should be obtained via CTSubscriberInfo.subscribers() .

I filed a feature suggestion years ago, FB12745207. It remains open to this day. I know that similar feature requests have been filed by large well know companies.

No. Carrier apps can use a private api to detect the phone number, but there's no public api available to do that.

You can't prevent the app from moving to the background.

I've been using RN in a large app for a few years. The larger and more complex the project becomes, and especially the more and more things that get implicitly and explicitly pulled in by RN then the more and more and more unstable Xcode becomes in being able to compile it, and then run it. I can't speculate from what you've posted what the issue is, and am not familiar with that framework being used, but from experience if you clean everything (I mean everything, including deleting the node_modules folder and the pods folder and everything in Xcode) and restart the Mac then there's a 95% chance issues go away.

Yes it does, I forgot to select the All tab, its set to the Basic Tab by default

Well that's impossible. An iPhone app doesn't have the capability to detect an incoming call never mind listen to the content. Apple themselves of course would have the ability to do this, but not anybody else unless they have a server integrated with the telephony system. An Android app could with certain permissions, but that's not for this forum.

I have the same problem. Also iOS 17's CTSubscriber.simInserted() has stopped working in iOS 18. So forwards compatibility has been broken (apps released using CTSubscriber.simInserted() no longer work).

I've never encountered any CPU restrictions with an extension. So maybe it is running out of memory. You have enough memory to load the array, but then maybe you are consuming more memory as you process the array. If you run/debug the extension (as opposed to running/debugging the app) in Xcode you can monitor the memory usage in real time just as you can with the app. I think from memory the memory limit is 20Mg, so you can see if you are getting close to and then hitting this limit (if you go over while running the extension in Xcode then it'll tell you) If you are running out of memory then you can try using autoreleasepool {} during processing to free memory. The OS churns out a lot of logging, if you search in the log console (not Xcode's log console) for your extension bundle id while its running, the OS will probably log what the problem is. Or as mentioned above, run the extension in Xcode and that'll probably tell you what the issue is.

The extension has a set memory limit, which is much less than that of an app. Why can you not do the iteration in the app when it first launches rather than the extension? (the extension is not part of the app, it is separate from it but data from the iteration process can be shared via the filesystem for example). Also an extension doesn't simply run for 30 seconds, it will run until the completion handler is called, if the handler is not called within 30 seconds then the system will call the handler for you. If you have to do the iteration within the extension, you will need to delay calling the completion handler until the iterations have completed. If that takes longer than 30 seconds, then that's another good reason why you need to look at doing this in the app rather than the extension. You say the iteration is part of the initialization process, hence its a one time operation, why therefore cannot it be performed by the app (I use the term app to not include the extension) the first time the app runs, and then the results of that made available to the extension?

If you google you've easily find instructions on how to do it. Basically put your phone into recovery mode and plug into a Mac and restore it. However I've been trying to do this myself and I just absolutely cannot put the phone into recovery mode (the same phone which in the past I have been able to many times). Perhaps there is a problem with iOS 18 beta that prevents it from being able to put it into recover mode.

Posted as FB13844575

This has been reported elsewhere on the forum, somebody from Apple replied saying it was a known issue. I think they said it was in iOS 17.2.1 and the fix was to update to 17.3, but maybe I missremember that as you say you've also seen it in 17.5.1

If you don't know/understand what "We were still unable to review your app as it crashed on launch.", for some reason, why not just say "I don't understand what We were still unable to review your app as it crashed on launch means". If you do understand what it means, they why post it with no further details? I just don't get it, how can you possible be hoping for any help from this forum with this?

Why? I mean just why would you post something like this? You and the hundreds of others that do similar. Is this a question you've posted, no it is not. Is this a request for assistance/help/comment you have posted, no it is not. Is there any useful information you have attached or added, no there is absolutely nothing at all. Do you really think you will get some feedback on this? What will posting quote from Apple review achieve. Nothing. Nothing at all. Good luck