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
.startDirectChat(
mxId,
preset: CreateRoomPreset.trustedPrivateChat,
enableEncryption: false,
initialState: [
StateEvent(
content: {
'history_visibility': HistoryVisibility.worldReadable.text, //wanted joined, but still same issue
},
type: EventTypes.HistoryVisibility,
),
],
)
When creator sends a message in that room, then invitee sees username and no message, upon clicking on that conversation, i get error: Tried to request history without a prev_batch token
I need to see messages before accepting the conversation to prevent spam.
upon accepting conversation, i see messages.
Steps To Reproduce
invite someone
see no message
cannot see any events in timeline
exception
Screenshots or Logs
No response
Security related
No response
The text was updated successfully, but these errors were encountered:
I need to see messages before accepting the conversation to prevent spam.
This is not possible. As you can see in the spec here the matrix protocol doesn't allow taking a look into the timeline. However it is possible to set the reason field when sending an invite. Be aware that this would be not end to end encrypted
Checklist
In which Project did the bug appear?
Other
If you selected "Other" as Project, please enter in which project the bug occurred.
SDK
On which platform did the bug appear?
Android, iOS
SDK Version
29d982b
Describe the problem caused by this bug
im using this for private conversation:
When creator sends a message in that room, then invitee sees username and no message, upon clicking on that conversation, i get error:
Tried to request history without a prev_batch token
I need to see messages before accepting the conversation to prevent spam.
upon accepting conversation, i see messages.
Steps To Reproduce
Screenshots or Logs
No response
Security related
No response
The text was updated successfully, but these errors were encountered: