Is it possible to use a blank BGTaskRequest just to get the action of the app launching and then do your processing in the main app constructs instead , eg. AppDidFinishLaunching. This way you're not constrained to the tasks time limits set out by Apple. In general, I am confused about the purpose of using the BGTasks if the app will launch and you can start doing what you want in the main code body instead.

I know that if a user force quit the app, the system will not relaunch the app upon a silent notification. But, the opposite is true if the app is subscribed to location service ("always allow" permissions) and there is a location update. The app will be launched in background even if it is force quit. So my question is, if user force quit the app, and then it is launched in background due to location updates, will that reopen the door for the app to be launched in background due to silent push notifications. Can location service update be used as a get out of jail card? If not, will silent push notifications be sent nonetheless when the app is open in background due to a location service event.

What is the expected change in distance that will trigger significant change. In the documentation it says 500 m or more. can someone provide an upper limit? and what is the average distance.