Hi I have the same problem in my app. I need to be able to use startUpdatingLocation with a distance filter set (200m) without setting the showsBackgroundLocationIndicator flag to true. My app needs to, in the background, be able to determine deltas in the user's location to figure out if a user is travelling or not. I'd use the CoreMotion API but that's also limited in the background, and from my testing only works when the locations are coming through in the background as well, so I am using a combination of both. Using the significant change monitoring service is not reliable or frequent enough, by the time that my app MAYBE gets a location update through that service, I've missed out on half of the trip. Also, it seems that region monitoring has the same problem, I tried to implement it but my app stops receiving locations in the background. Please help, this is quite urgent and is clearly causing breaking changes for everyone affected. It's pretty inaccurate that my app now has to show a location pill indefinitely to users throughout the night or during the day when their location isn't even changing enough for me to use it. I can understand if the pill shows when my app starts receiving locations and goes away when my distance filter is no longer being exceeded, but this it really excessive. Also, it's counter intuitive that my app can receive locations freely with no distanceFilter set in the background without notifying the user about this with the pill? As a developer, I'd expect better communication from Apple to its developers of changes such as this that have the power to completely break apps. And clearly this change wasn't thought through very well.