We're using TestFlight to distribute and test builds for our game. In doing so, we build a .pkg, send it to TestFlight, and when it's ready, it'll install the .app into the Applications directory.
On any MacOS computer that's used for development and, has at any point created a .app itself, TestFlight ends up in a permanently broken state for that particular application.
The following issue occurred to numerous developers:
Install TestFlight
Install any version of our game and it runs fine
Build a copy of the .app locally to test in-progress work.
Attempt to launch the TestFlight build again
The TestFlight version of the .app doesn't launch and there are no errors or dialogues. It just bounces once or twice in the taskbar then stops.
We have tried every combination of the following:
Deleting the development builds of the .app
Reinstalling the TestFlight builds
Reinstalling TestFlight itself
Reinstalling all development tools used in creation of the .app
Deleting all traces of the .app we could find anywhere on the machine
Nothing works to fix the issue and the computer is left in this broken state until macOS is completely reinstalled.
0
1
680