CrashReporterExtension runtime capabilities and limitations

Question

Created 1d

Replies 1

Boosts 0

Participants 2

This post is from the WWDC26 Power & Performance Q&A.

The documentation suggests that you can transfer files out of the crash reporting extension but it doesn’t outline if there are any gotchas to watch out for.

Are there any limitations to this?
Does it have full network access?
Are app groups and keychain groups fully supported?
Does the extension have a memory footprint limit we should watch out for?
What is the lifecycle of the callback, what Is a reasonable amount of time to plan our implementation to do its work and be done within? 10 seconds? 30? And so on.

Answer 1

Security Engineer OP

Apple

1d

Hi!

Thanks for the questions. This is a new extension that does have some limitations.

Yes, there are some limitations such as the timeout in your question 5, if you have any other follow up questions about limitations, please let me know.
The extensions do have network access, essentially running in the same environment as your app.
What are you looking for specifically in app groups? The way the extension works is the crash reporter filters on developer ID and bundle identifier, not specifically by App Groups, but if you share a developer ID, you could potentially have one extension service more than one app. For example, if your app is named com.example.myapp, an extension for com.example.myapp.crashreporter will respond and be sent the task port.
There is a memory footprint limit, but it is shared by the crash reporting system. I don't think will be a problem, because the limit is quite generous.
There is a timeout of 60 seconds (wall clock) before your extension will be evicted.

If you have any follow up questions, please reply to this thread.

Jeff