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
Describe the bug
v1/conversations/list/v2 API in 2023-10-23 (Chart Release 4.39.0) release。returnes the data structure with new access_role logical.
"access": [
"invite",
"code"
],
"access_role": [
"team_member",
"non_team_member",
"guest",
"service"
]
so the iOS APP cannot correctly process the data returned by the v1/conversations/list/v2 API. To Reproduce
Steps to reproduce the behavior:
Expected behavior
V1 API maintains the original logic
"access": [
"invite",
"code"
],
"access_role": "non_activated",
"access_role_v2": [
"team_member",
"non_team_member",
"guest",
"service"
],
The text was updated successfully, but these errors were encountered:
oomhj
changed the title
v1/conversations/list/v2 The V1 version API returnes the data structure with new access_role new logical
v1/conversations/list/v2 The V1 API returnes the data structure with new access_role logical
Nov 27, 2023
Describe the bug
v1/conversations/list/v2 API in 2023-10-23 (Chart Release 4.39.0) release。returnes the data structure with new access_role logical.
"access": [
"invite",
"code"
],
"access_role": [
"team_member",
"non_team_member",
"guest",
"service"
]
so the iOS APP cannot correctly process the data returned by the v1/conversations/list/v2 API.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
V1 API maintains the original logic
"access": [
"invite",
"code"
],
"access_role": "non_activated",
"access_role_v2": [
"team_member",
"non_team_member",
"guest",
"service"
],
The text was updated successfully, but these errors were encountered: