Closed brentsimmons closed 1 year ago
I've looked at this one every which way. I've run every possible test scenario that I can. I think it comes down to either we are calling a completion handler twice in our Account.update
(or below in the database) or it hung while somewhere in Account.update
.
The way that the call stack looks, it looks like a completion handler is getting called twice somewhere. I'm not having any luck finding it as I audit the code though. I'll keep looking...
This crash appears just once in our crash logs, so I’ll de-milestone it. We’ll call it a fluke for now.