No, I didn't try that because with the latest project I sent I have 5 other machines on our team that can reproduce the issue. The common factor seems to be some version of the M1 chip. We have 4-5 people with M3 that cannot reproduce and one person with an M2 that cannot reproduce.

Also, for the record, we do see this bug on M3 machines with our production code-base. Since the bug has to do with the file structure of the package, and with the code in at least 2 source files, I don't know what the file structure needs to be to reproduce on an M3. I wasn't aware this was processor-specific when I was tearing our project apart looking for the trigger. Hopefully fixing this bug with the reproducible case on an M1 will also fix it for all cases.

I tried with a brand new user as you asked and it reproduces in that environment as well.

Thank you for your diligence on this issue Quinn!

FB17252543