getting "no app-db changes caused by" for a lot of handlers that should have produced a diff

What common mistakes should I watch for?

can you provide an example for a specific handler @alqvist ?

not a good example though: http://pastebin.com/vtnW0NW7

mayhap it has something do with user action vs callbacks from Sente

It seems I can’t use add-watch to monitor re-frame subscriptions if the subscriptions aren’t dereffed in any component. Is that correct? I’m running my React Native headlessly and thus don’t have any React components mounted.

@alqvist could it be that the value of db after the merge just so happens to be = to the original value of db? Hence nothing changing?

Ie, are all these events already in db somehow, from before? OR events might be nil or an empty collection.

Wild guessing. Can't see anything wrong with the pasted code.

@vikeri that sounds about right, although I've never tried it.

@mikethompson Alright, so no way of monitoring a reaction without dereffing it in a component? Any ideas of how I should solve it then? I would like to reuse as much of my re-frame logic as possible.