Since it couldn't reproduce the issue in the iOS simulator, I had to run it on the device, reproduce the issue, and provide the logs. This went on for many rou

Since it couldn't reproduce the issue in the iOS simulator, I had to run it on the device, reproduce the issue, and provide the logs. This went on for many rounds, during which I tried to steer it toward what I thought was the source of the bug, while the model mostly kept adding instrumentation and logs. In the end the cause was not what I suspected, but reasonably close to it via another mechanism.