Not in this case, as it's not code explicitly called by the client, but automatically loaded on app launch...

Yes, but 1. it’s hard to inject that as the crash happens very early at launch and 2. Objective-C exceptions of this type are not intended to be caught.

That's not strictly true, and anyway it's different for the app developer versus a library provider. If you're making a 3rd party SDK that can throw, you need to make it can catch those throws.

NSInvalidArgumentException is not intended to be caught. You can, of course, but receiving one indicates a serious run-time error.

If it's an objective C exception, you can catch those with an objective c wrapper function. Ive done that before in my Swift projects.