@mattl proposed a workaround on his open StackOverflow ticket: https://stackoverflow.com/q/58298439/5922449quoting his solution:"I could drastically increase the duration before the application gets moved to the suspended state, by reducing the resources consumed in the background. -> I removed the motion collection completely from the app. -> When shifting into background I decrease the accuracy and increase the distanceFilter for locations to get less events, I stop some tasks that are updating the UI, I downsample the collection of other data sources, I do no exports of my data in the background or other workload. So now i get around 3000 minutes in the background."@mattl, how much did u decrease your distance filter and accuracy parameters? and how much is your background trip path detection affected by those changes?

When user responds to the location permission system alert, CLLocation delegate method "locationManagerDidChangeAuthorization" is triggered. You can handle the user response there. For more info, check: https://developer.apple.com/documentation/corelocation/cllocationmanagerdelegate/3563956-locationmanagerdidchangeauthoriz