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
ConversationsV1.PageConversation does not work when trying to fetch next page with a pageToken and pageNumber. It always return an empty result.
Cause of the problem: Conversations api returns a pageToken like PTclosed_2024-01-18T03:17:17.005Z_CHa09ace6334284f0aa7f988ebad3e231a while other endpoints return a hashed token like this ENZXlKbGRtVnVkRjlrWVhSbElqb3hOekEyTlRBek1qVTJNREF3TENKemFXUWlPaUpCUlRFek5tVXpOekJpTXpoak1tTTRPR1ptTVRRMU1EWXhNMk15TVRNME1HTXhJbjA9
The .005 inside Conversation pageToken will be eliminated in the SendRequest method in client.go which breaks the token.
Steps to Reproduce
1, call PageConversation method with empty pageNumber and pageToken
2, parse the response and get pageNumber and pageToken for next page
3, call PageConversation again with pageNumber and pageToken for next page.
Technical details:
twilio-go version: 1.17.0
go version: 1.21
The text was updated successfully, but these errors were encountered:
Issue Summary
ConversationsV1.PageConversation does not work when trying to fetch next page with a pageToken and pageNumber. It always return an empty result.
Cause of the problem: Conversations api returns a pageToken like
PTclosed_2024-01-18T03:17:17.005Z_CHa09ace6334284f0aa7f988ebad3e231a
while other endpoints return a hashed token like thisENZXlKbGRtVnVkRjlrWVhSbElqb3hOekEyTlRBek1qVTJNREF3TENKemFXUWlPaUpCUlRFek5tVXpOekJpTXpoak1tTTRPR1ptTVRRMU1EWXhNMk15TVRNME1HTXhJbjA9
The
.005
inside Conversation pageToken will be eliminated in the SendRequest method in client.go which breaks the token.Steps to Reproduce
1, call PageConversation method with empty pageNumber and pageToken
2, parse the response and get pageNumber and pageToken for next page
3, call PageConversation again with pageNumber and pageToken for next page.
Technical details:
The text was updated successfully, but these errors were encountered: