Dale
Dale
We are seeing this error regularly: ``` ⚙️ Generating plists... ⚙️ Generating project... Fatal error: Duplicate elements of type 'PBXFileElement' were found in a Set. This usually means either that...
We've run into an issue where we are getting some kind of race condition, so we increased logging to try and debug. It made sense to contribute it back. None...
I opened a very similar ticket months ago: https://github.com/peripheryapp/periphery/issues/245 and it had a clear fix. Unfortunately, I'm (still?) seeing inconsistent results between runs (again?). This time, I can run it...
**Describe the bug** I was playing around with a puzzle and got into a state where I only ever get the output "[Object object]". No matter which steps I disable...
**Describe the bug** The binaries for the latest release don't appear to be signed correctly for macOS. When trying to run, I had to manually approve every single binary to...
### Environment Information - **Platform**: - [x] iOS - [x] macOS - **Package version(s)**: All - **Xcode and OS versions**: All ### Please provide a reproduction of the bug: Basically...
If the simulator fails for whatever reason then the output isn't captured. Here's a sample (test names and classes replaced with `snipped`): ``` Test Case '-[snipped]' passed (0.416 seconds). Test...
We have thousands of tests and it's very difficult to see which one(s) failed when we encounter a failure. A summary at the end of the output with these failed...
`N` defaults to 10 for warnings and 7 for errors, but is configurable. Why do we want/need this rule? Swift relies heavily on closures and it's very easy to end...
The purpose of this change is to introduce the tools and show that they have no effect with all rules disabled. The rules that are chosen can be very contentious...