There seems to be a bug with removing a user from the roster when their subscription is rejected, the removed user temporarily appears as if they were accepted. I'm using the CoreData storage method and these are steps to reproduce the problem:
If I close the app and reopen it triggering a disconnect/connect then the table is cleared up and everything looks as it should.
Anyone come across this before?
I think this may have been the same issue as #186 , could you recheck to see if the XMPPRoster now works as expected?