message_changed event inside a shared channel from external user
See original GitHub issueDescription
I am able to respond to all message_changed events in a channel within my workspace. However, when the bot is invited into a shared channel it seems to only be able to receive events from external users for an initial message/thread, and nothing is received when someone from another org changes any of their messages/threads.
What type of issue is this? (place an x
in one of the [ ]
)
- [ x] bug
- enhancement (feature request)
- question
- documentation related
- testing related
- discussion
Requirements (place an x
in each of the [ ]
)
- [x ] I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
- [ x] I’ve read and agree to the Code of Conduct.
- [ x] I’ve searched for any related issues and avoided creating a duplicate issue.
Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 2.3.0
node version: v14.5.0
OS version(s): osx 10.15.7
Steps to reproduce:
- create bot in workspaceA
- invite bot into shared channel with workspaceB
- have user in workspaceA write message in shared channel
- bot will see message
- have user in workspaceB write message in shared channel
- bot will see message
- have user in workspaceA change their message
- bot will see changed message
- have user in workspaceB change their message
- bot will NOT see any event about the message change
Expected result:
expected to see message event with subtype of message_changed for user from workspaceB as the change is visible and public
Actual result:
no event is recorded when user in workspaceB changes any of their messages or threads but the message event is received on any INITIAL message or thread
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Quick follow-up for anyone coming across this, later on, it turned out the workspaceB was NOT a paid workspace but was on a trial for 90 days. When the bot was active on shared accounts between two paying workspaces everything worked fine. Platform support is going to look at it as a bug to be fixed but I didn’t have a particular need to handle trial workspaces anyway so the revelation unblocked me.
Platform support is actively working on the issue with us. We think there is some sort of bug at that level so this issue should probably be closed so I will go ahead and do that. Thanks so much for those that attempted to replicate and led us to support!