Ekjot

Hi @ramon-san, thank you for taking the time to raise this issue as well as the extraordinary detail in describing the problem. We will investigate this issue and get back...

Hi @ramon-san, I have been able to reproduce this issue. It will be tracked as a bug and I will report back to this issue when we have a fix.

@malaquf Thank you for the interest in this feature. We are still tracking this feature request and comments on this issue move it up in our priority list. And of...

Thanks @MarlonJD, since I came to this issue late I didn't even see the pr you submitted, I'll review those changes soon. I see your point about the secondary index...

Hi @aalloul, I have attempted to reproduce this but I have been unable to, google and other external identity providers seem to work fine when I deploy a sample application...

I see @wxxedu , thanks for that info, its a good call for any future developers looking through this issue! Unfortunately it doesn't seem like this will be the case...

Hello @joshuamoreno1, currently Amplify Datastore v1 is in maintenance mode, I would recommend upgrading to v2 and see if the issue is resolved. Please see the [documentation for reference](https://docs.amplify.aws/gen1/flutter/start/project-setup/upgrade-guide/#datastore).

Hey @giulitu95, apologies for the inconvenience caused by this error being thrown when you don't want to track it! Currently this is the expected behaviour, however we will investigate if...

Hi @lokalathlet , to clarify, you noticed this behaviour with the device time after the user has signed in with web-ui?

Thanks for the clarification, we are still investigating including communicating with the other Amplify library teams to determine a fix