Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
lol. Reminds me of a bug I fixed once in an iOS app. We were fetching a list of ‘recently viewed’ from the web api and storing them in CoreData. The problem was if you opened a Patient record after viewing that screen, the document structure was all messed up, docs appearing in the wrong folders etc.
The cause? somehow saving the recent patients was overwriting and corrupting the existing record for that patient.
The solution? Delete the code that saves the recent patients result to the DB. There was basically no need to do it, since if the user was offline, they couldnt view that screen anyway, or open any patient they hadnt saved earlier.
mebekix3469dYou Sir. You are a Hacker.