Dale

Did this ever go anywhere?

It's definitely not my area of expertise, so I wouldn't have much ability to do so. What I was curious about though was the custom uncaught exception handler. It's pretty...

As an update, we tried that fix with the callbacks and it's working perfectly for us. It probably won't work perfectly 100% of the time due to the nature of...

It's an hour per run, so I'll script something on Monday to run some serious tests and see what we get.

We never skip the build. It's always clean. And the full build and scan takes an hour. :)

That's the eventual goal. We have 2 "phases": 1. We ran an initial scan, which generated those 3900 results. We added these as comments directly to the source code. 2....

So I've run the same scan 5 times and looked at the diffs (10 of them in total) and there _is_ a pattern, but it's not clear. No two diffs...

A consistent bug is easily dealt with :) What I don't understand is why it isn't consistent. I assume that at a high level Periphery basically follows these steps: 1....

It's literally just declared like: ```swift private enum Whatever { static let someProperty = "some_value" } ``` And then used like: ```swift func doThing(someProperty: String?) { var myDict: [String: String]...

No worries, I've also been busy which is why I haven't looked any deeper either.