Latest Chime SDK(Messaging) is not compatible with old app instance arns

[VibinGowtham]

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?

• [X] GitHub issues
• [X] FAQs page
• [X] README page
• [X] Feature-specific guides

Reproduction steps

1. Create an appInstanceArn using "aws-sdk": "^2.1377.0"
2. Once created, Update the sdk to "@aws-sdk/client-chime": "^3.503.1" and use ListAppInstances API call to list the instances
3. Despite having previously created an AppInstanceArn, the list appears empty.

Amazon 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