ashika112
ashika112
@mattiLeBlanc Got it. We are going to close this issue since there is no way for us to re-produce the exact issue and there is a workaround suggested. If there...
@mattiLeBlanc we have verified in web app this already. And we dont see an issue in that part at all.
Re-opening this to track the conversation. Will take a look at this soon and update.
@anthonyhoegberg Sorry for not getting back on this earlier. This would be a feature request for Amplify backend. However if you are using Amplify JS in your front end, you...
Curious: What happens when you dont dismiss it? Does other messages overrides the space?
@adamritolabs Yes, the base API will also need some update in order for this to work. We will post more updates in the ticket when we release the feature.
@kaestleo Hi, thanks for bringing this up. Let us look into how the same can be achieved in v6 or if this is indeed a gap and will provide some...
@StephanBradler Apologies for the delay. So we think this might be achievable in current v6 architecture too but might not be as strightforward. I am putting together a sample code...
Hi @kaestleo @StephanBradler , providing some more update here. Before going into the solution, I want to make sure understanding for this is laid out right. CredentialsProvider is always in-memory...