Guo Ling
By the way, I found that the order of your logs is questionable. For one example, >"2022-03-21T16:44:30.864Z",loadFromFile,"loaded [snb.userdefault.store] with 86 key-values" "2022-03-21T16:44:30.864Z","-[MMKV onMemoryWarning]","cleaning on memory warning snb.userdefault.store" There's no 'loading...
And you should provide thread info/thread id for each line of log.
That's very vivid logs you provided. However, the order is still questionable. I have filtered out all info relative to the corrupted file: >2022-03-25T02:53:58.537Z,loadFromFile,loading [com.xueqiu.dataCache] with crc 444446063 sequence 916...
Noted.
I'm sorry to say that due to my limited knowledge of flutter testing, the unit test for the package is not provided in the latest version (v1.2.12). I'm hoping will...
Your crash stack is **not** symbolized. It's impossible to further analyze this problem.
Google > > Your crash stack is **not** symbolized. It's impossible to further analyze this problem. > > What should I do for it?
Why there are only two call stacks? Looks like you have lost tons of stacks.
I don't quite understand your question.