SIGSEGV on state.didSet about reswift

[DivineDominion]

@mhamann Great, then I'll close this issue!

For some async tasks, try out https://github.com/ReSwift/ReSwift-Thunk/ to dispatch an action that can perform something complex, access the state in the process, and dispatch actions to indicate progress. Like the HTTP request/pending/result triad.

[DivineDominion]

Is there some other error code for a sub-category?

https://developer.apple.com/documentation/xcode/investigating-memory-access-crashes

Never had an iOS app crash tbh :)

Since you speak of race conditions: I do wonder if you do something odd around the use of createThunkMiddleware. I'd try to symbolicate the crash log first and inspect the call stack further.

[DivineDominion]

@mhamann Did you figure out a cause for this?

[mhamann]

Thanks for checking in @DivineDominion. I must've missed your original reply. We did solve this. We were using Combine within an Actor, and that seems to have been the trigger for this issue. Somehow, the Actor's subscription to the store was causing memory to be accessed in an unsafe way, and thus the sigsev crash.

My iOS dev knowledge isn't deep enough to know whether or not there is a good way to solve this, but we ended up moving the code from our Combine logic into ReSwift middleware. It ends up making the dispatch flow async, which is somewhat annoying, so other approaches might be better.