Multi-client roster approval synchronization issue #671

Activity

1. chrisballinger

   added

   Bug

   on Jan 27, 2017
2. chrisballinger

   added this to the 4.1 milestone on Jan 27, 2017
3. chrisballinger commented on Mar 25, 2017

   

   chrisballinger

   on Mar 25, 2017

   MemberAuthor

   More actions

   This is possibly fixed in latest commits 08fd59d e74b8e7
4. chrisballinger

   closed this as completedon Mar 25, 2017
5. mmehrle commented on Dec 12, 2017

   

   mmehrle

   on Dec 12, 2017

   More actions

   This issue is still plaguing me.
6. chrisballinger commented on Dec 12, 2017

   

   chrisballinger

   on Dec 12, 2017

   MemberAuthor

   More actions

   @mmehrle I still see this too occasionally. I think it's because we aren't handling roster push properly.
7. chrisballinger

   reopened this on Dec 12, 2017
8. mmehrle commented on Dec 13, 2017

   

   mmehrle

   on Dec 13, 2017

   More actions

   BTW, I'm a noob with this although I'm pretty technical. Running the latest version of ejabbered with:
   mod_push: {}
   mod_push_keepalive: {}

   mod_stream_mgmt:
   resend_on_timeout: true
   ack_timeout: 10
   resume_timeout: 0

   I hope this is set correctly. But apparently I was mistaken to assume that push already works in the currently deployed version of ChatSecure.