Thomas Ricouard

Relevant part of the crash log ``` Application Specific Information: BUG IN CLIENT OF LIBDISPATCH: trying to lock recursively Filtered syslog: None found Thread 0 name: Dispatch queue: com.apple.main-thread Thread...

After some more investigation, it seems like it's the reducer code which is problematic, for some reason, if you access other part of your state (substate) in your reducer it...

I've discussed with an Apple engineer working on the Swift compiler. Basically I've turned off optimisation on two reducers with annotations `@_semantics("optimize.sil.never") ` And now the app work in release...

I must admit I didn't took (yet) the time to do that. But I'll for sure. Need to pinpoint the issue before shipping to production.

About the timer... well, it's there for now because I have no better place, and since I'm on a serial thread for my whole store, I have no issue. It's...

I never got that problem again when I properly got out my store.states out of my reducers and middleware (out of everywhere actually). It was just bad coding on my...

Yes, I've removed any reference to store. in my reducers and middleware.

@johnnysparks Yeah, in my case I'm just dispatching action and my views/controller don't care about the loading state etc.... juste subscribed to the specific state and wait for the data...

Ah yeah SkipRepeats is currently not merged with master: https://github.com/ReSwift/ReSwift/pull/203 All my state implement Equatable, so using the skipRepeat branch, I can subscribe to substate and only be notified when...

@DivineDominion I did that mostly because the code is kept super simple. I have now pure Action for my "set" actions, and ActionsRequests. Sure my ActionsRequests are not necessarily reduced...