I'm experiencing a strange behaviour in my app. Behaviour is as follows:
For a while, everything works. Then, intermittently, after an unspecified amount of time, the app gets into a state where NSFetchedResultsControllers do not behave properly.
Insert/change messages are not received.
When looking at a screen driven by an NSFetchedResultsController, initially some new changes will be reflected, but after a moment the records that were inserted disappear.
*Backing out and back in to the ViewController generally refreshes, and either looks right or repeats the above.
This issue is not reliably reproducible, and takes our QA department a while to make happen again, but it is definitely related to MagicalRecord 2.2. Is this anything anyone has experienced? Reverting to 2.1 fixes the problem. I'd like to not be stuck with 2.1 forever.
I'm experiencing a strange behaviour in my app. Behaviour is as follows:
For a while, everything works. Then, intermittently, after an unspecified amount of time, the app gets into a state where NSFetchedResultsControllers do not behave properly.
Insert/change messages are not received. When looking at a screen driven by an NSFetchedResultsController, initially some new changes will be reflected, but after a moment the records that were inserted disappear. *Backing out and back in to the ViewController generally refreshes, and either looks right or repeats the above.
This issue is not reliably reproducible, and takes our QA department a while to make happen again, but it is definitely related to MagicalRecord 2.2. Is this anything anyone has experienced? Reverting to 2.1 fixes the problem. I'd like to not be stuck with 2.1 forever.