News for hackers. Stuff that matters.
Re:App suddenly crashing on startup due to FBSDKRestrictiveD... by XCSme on Friday July 10, 2020 @10:56AM (#23792099)
So there is no way to try {} catch {} it, right?
Re:App suddenly crashing on startup due to FBSDKRestrictiveD... by Sephiroth87 on Friday July 10, 2020 @11:00AM (#23792156)
Not in this case, as it's not code explicitly called by the client, but automatically loaded on app launch...
Re:App suddenly crashing on startup due to FBSDKRestrictiveD... by saagarjha on Friday July 10, 2020 @12:02PM (#23792892)
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.
Re:App suddenly crashing on startup due to FBSDKRestrictiveD... by robterrell on Friday July 10, 2020 @12:54PM (#23793516)
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.
Re:App suddenly crashing on startup due to FBSDKRestrictiveD... by saagarjha on Friday July 10, 2020 @01:05PM (#23793659)
NSInvalidArgumentException is not intended to be caught. You can, of course, but receiving one indicates a serious run-time error.
Re:App suddenly crashing on startup due to FBSDKRestrictiveD... by valuearb on Friday July 10, 2020 @11:59AM (#23792865)
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.