back

by magnetic·7y ago·view on hn ↗
That was my understanding, hence my question. I don't understand how such app can affect another app (which is what the parent was complaining about I think).

Also I'm confused as to why my question was downvoted... I'm a dev too who's released a few sandboxed apps (on iOS and macOS) and would like to understand if there is a vulnerability in the sandbox somewhere. Seems like this would be useful to understand for many devs.

1 comments
No, there's no vulnerability in the sandbox. What is happening is that people are grabbing copies of an app, adding code to it (usually, by adding a new dynamic library and forcing the main binary to load it), and then distributing the modified app outside of the App Store. Any crashes in the modified app will still be reported to the original app developer, since aside from the small (or maybe not so small?) tweaks that were made the app functions like it normally would.
Aren't the crash-logging identity of the app, the sandboxing, the developer's identity and the code signing certificate all locked together?
I'm pretty sure everything is just linked to the bundle identifier.