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
AmazonChimeSDK uses expired chime credentials even after providing the new chime credentials.
To Reproduce
Steps to reproduce the behavior:
We have put 15 min timeout for chime credentials expire time from backend.
After expiring the credentials we will taking new credentials and trying to intialise the SDK again.
It will give The Security token an expired exception in getSessionEndPoint() function and we have debugged your SDK we have seen, the SDK is still using expired credentials even when we are passing new credentials.
Expected behavior
After the chime credentials expire and are initialised with new credentials, The SDK must need to use new chime credentials instead of expired credentials.
ChimeSDK Version
I am using 'AWSChimeSDKMessaging', '~> 2.36.3' this version
The text was updated successfully, but these errors were encountered:
Describe the bug
AmazonChimeSDK uses expired chime credentials even after providing the new chime credentials.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After the chime credentials expire and are initialised with new credentials, The SDK must need to use new chime credentials instead of expired credentials.
ChimeSDK Version
I am using 'AWSChimeSDKMessaging', '~> 2.36.3' this version
The text was updated successfully, but these errors were encountered: