I'm building an iOS framework where only a single header file is exposed, and the rest of the code is private. Within Xcode I have all objective-c exception breakpoints on, so normally when there's an exception I'm brought to where it occurred in the code.
During testing in a totally new project that is using this framework I created, every now and then when an exception is raised inside the framework, I'm brought to the otherwise private framework code, which is obviously not what I want.
I think this may be because the actual raw framework code/project exists in my environment and wouldn't occur for another person using my framework without access to the actual files, but unfortunately I don't have any way to currently test this theory. Does anyone know if this is something I need to be handling in order to truly keep the project files private that I intent to, or is this just a function of having the code exist locally?
I was able to get in another dev environment with a fresh project to drop in the framework and force an internal framework crash and it appears that if the otherwise private framework files exist on the same environment and a crash occurs when you have objective-c exception breakpoints enabled it will open the private framework file in question, BUT if you don't have those private framework files (which consumers of your framework wouldn't) you will simply be taken to the normal crash/stack trace view like below: