You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Synapse receives an event that is directed at/sent by an appservice user, it ensures the appservice has registered the user by hitting the /users appservice API. This check is not done during profile requests, however. This means that when clients try and do profile lookups before invites (such as in the case of riot: element-hq/element-web#7922), they might not bother with the invite because the user doesn't exist.
TLDR: Synapse should be hitting an appservice's /users endpoint during profile lookup requests too.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #4310.
Related: #4143
When Synapse receives an event that is directed at/sent by an appservice user, it ensures the appservice has registered the user by hitting the
/users
appservice API. This check is not done during profile requests, however. This means that when clients try and do profile lookups before invites (such as in the case of riot: element-hq/element-web#7922), they might not bother with the invite because the user doesn't exist.TLDR: Synapse should be hitting an appservice's
/users
endpoint during profile lookup requests too.The text was updated successfully, but these errors were encountered: