I wrote the example later without re reading the definition I gave.. that was confusing! Fixed it, thanks!

You could add stack sampling in production with Debug.startMethodTracingSampling() (works in releases) with a low sampling rate, then upload the file from the device. Alternatively, you could track attributes (account, device type, entry point, etc) and then try to repro locally and once you repro a slow hot launch you can profile locally.

Because canceling the request means we can save network related resources

Yeah the general idea here is that this ensures you add an activity to a specific activity stack, rather than starting it from a random live activity or from the application context which isn't tied to a specific activity stack.

Starting an activity from the Application class isn't the same as starting it from an activity. When using the application class the activity manager doesn't know which activity stack the new activity should be added to.