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
After migrating from "aws-sdk": "^2.1377.0" to "@aws-sdk/client-chime": "^3.503.1", I've encountered an issue regarding the listing of old appInstanceArns when using the ListAppInstances API. It appears that the previously created appInstanceArns are not being displayed, unlike the ones generated with "@aws-sdk/client-chime": "^3.503.1". Is this expected behaviour? If so, what steps can we take to preserve the old appInstance channels and messages and continue operations on them? Any guidance on this matter would be greatly appreciated. Thank you.
What happened and what did you expect to happen?
After migrating from
"aws-sdk": "^2.1377.0"
to"@aws-sdk/client-chime": "^3.503.1"
, I've encountered an issue regarding the listing of old appInstanceArns when using the ListAppInstances API. It appears that the previously created appInstanceArns are not being displayed, unlike the ones generated with"@aws-sdk/client-chime": "^3.503.1"
. Is this expected behaviour? If so, what steps can we take to preserve the old appInstance channels and messages and continue operations on them? Any guidance on this matter would be greatly appreciated. Thank you.Have you reviewed our existing documentation?
Reproduction steps
"aws-sdk": "^2.1377.0"
"@aws-sdk/client-chime": "^3.503.1"
and use ListAppInstances API call to list the instancesAmazon Chime SDK for JavaScript version
"@aws-sdk/client-chime": "^3.503.1"
What browsers are you seeing the problem on?
Browser version
Meeting and Attendee ID Information.
Browser console logs
The text was updated successfully, but these errors were encountered: