Skip to content

Fetching message from history - messages coming with null timeToken #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
devopsokdone opened this issue Aug 25, 2020 · 2 comments
Closed
Assignees
Labels
status: done This issue is considered resolved. type: bug This issue reports a bug. type: documentation This issue requests a change in documentation.

Comments

@devopsokdone
Copy link

devopsokdone commented Aug 25, 2020

Messages fetched from history coming with null timeToken.

BatchHistoryResultEntry object obtained from fetchMessages api has the field timetoken as null.

@are are self-assigned this Aug 25, 2020
@are are added status: in progress This issue is being worked on. type: bug This issue reports a bug. labels Aug 25, 2020
@are
Copy link
Contributor

are commented Aug 25, 2020

Hi! Thanks for reporting the issue. We have a release coming soon, so I will include a fix for that in it.

@client-engineering-bot
Copy link
Contributor

@devopsokdone this issue is addressed in v2.0.0

@client-engineering-bot client-engineering-bot added status: done This issue is considered resolved. type: documentation This issue requests a change in documentation. and removed status: in progress This issue is being worked on. labels Aug 31, 2020
@Adidi Adidi mentioned this issue Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: done This issue is considered resolved. type: bug This issue reports a bug. type: documentation This issue requests a change in documentation.
Projects
None yet
Development

No branches or pull requests

3 participants