This just started happening to me two days ago. It's an old Xcode project (2014!) that uses MapKit, last updated in June 2018. I run it to compare its behavior with the new app I'm working on that replaces it.
I was running it off and on for weeks without trouble in iOS 13.x Simulator, using GPX files to simulate user location (including moving locations). I have multiple copies of Xcode installed (every major point release from 11.7 back to 11.2) as well as two versions of Xcode 12 (beta 6 replacing beta 4). None of this seemed to bother it.
Then the problem started happening with no precipitating event I can identify, and now I find any copy of the project (even a fresh clone from source control) has the exact same behavior, so whatever this is, it's external to the Xcode project itself. And it happens in every Xcode version I've tried, all the way back to 11.2. (But not, at least yet, on devices, just Simulator.)
Specs: macOS Catalina 10.15.4 (19E266) on a MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports); 2.8 GHz 4-core i7; 16 GB of RAM, 1TB of SSD, Xcode 11.6 (and other versions).
Fortunately I have an older Mac with older macOS (Mojave) and Xcode (11.3.1) that doesn't (yet) show this bug, so I can rely on that for now. But I hope this does get fixed so I can return to comparing old and new code on the same machine.
Topic:
App & System Services
SubTopic:
Core OS
Tags: