I think this happens when you activate a post, then try to activate a different post from the same author.
Becoming more convinced that it's the common author that is somehow the culprit. Also, this is not a Facebook post issue. It happens with Twitter posts, too.
Also, social uses an old code path that creates stacks in top, and sends them to drawer. We could achieve more efficient results if we used a stack:create event instead, and delegated creation to the drawer, where a record of the stack may already be on hand for use.
Fixed by fixes for #746574.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Depends on: 746574
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.