Regarding using notification to test the behavior, the idea is nice, but the slight problem is that it requires somebody closely watching the phone to quickly react to unpredictable background fetch event. Not really. The sysdiagnose capture covers a very long period of time (hour to days, depending on circumstances) so as long as the device hasn't been rebooted* it doesn't actually matter when you collect the log. While closer in time is theoretically better, for an issue like this there isn't really any practical difference between collecting a long immediately vs 30+ minutes later. *A lot of log data is purged at reboot, so that is a problem for this sort of thing. For most issue I actually recommend developer wait 5-10 min. after an issue before they trigger the log, as that makes sure that the log noise of the sysdiagnose isn't mixed in with any trailing log data. I'll also say that the upper time band here is pretty big. I don't like saying sure, collect it 4 days later because things do go wro
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags: