@rkast4321, I figured out why the offline caching is causing TrackerOnes to SOS. It is caused by a bug in littleFS flash file management library used in deviceOS, where when truncating a large file truncating begins in the wrong block. I am able to reproduce the SOS error at will as well, which was really helpful for figuring this out. Given this is much larger bug then just this offline caching use case, I started a fresh thread in the firmware category here
You can set up your trackers to recover from this error when it occurs using the System.resetReason() method referenced above as the first line in setup(), but will need remove the STARTUP macro - if Tracker::startup(); is called, when attempting to load the saved configuration settings from a corrupt file system, the device will SOS.