The customer is experiencing crashes on FSM 6u7 while synchronising messages. We applied a fix from R&D for that issue coming from u9, but it didn't fully solve the problem. The apps still crashes when there are a ton of messages to be syncd in the background.
Please note that even without Push Notification, the background sync often works. For some users it seems to not work very much in the background. Sometimes it stops altogether and the following gets logged under Privacy / Analytics:
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: application<com.FSM.Mobile.Superior>:360 exhausted real (wall clock) time allowance of 10.00 seconds | ProcessVisibility: Background | ProcessState: Running | WatchdogEvent: scene-update | WatchdogVisibility: Background | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 17.240 (user 17.240, system 0.000), 87% CPU", | "Elapsed application CPU time (seconds): 7.526, 38% CPU" | ) reportType:CrashLog maxTerminationResistance:Interactive>
Triggered by Thread: 0
This is caused by iOS killing the app since it deems the app is using too much CPU. The customer wants more reliable background synchronisation and we haven't discussed push notification yet. Any suggestions other than using Push?