MrMagic
MrMagic
We would also like to have this fixed. Currently having Google, Apple and Microsoft social login so the proposed work around will also not work for us. Please have this...
We also have a challenge now how to handle this in a nice way. We are thinking about using sessions storage to remember which social login button the user used....
> > We also have a challenge now how to handle this in a nice way. We are thinking about using sessions storage to remember which social login button the...
We are also experiencing the same issue. Haven't figured out how to fix this for mobile. Any suggestions or work arounds are welcome!
+1 here. What I have done now is not to auto-update amplify CLI to latest version during deploy which is default behavior. This gives us 3 minutes back of build...
> How do you do that? 1. Amplify console 2. Select project 3. Build Settings 4. scroll down "Build Image Settings" 5. Delete Amplify CLI from "live update packages"
> Yeah we're seeing 40-minute deployment times and it just keeps going up 😠> > [aws-amplify/amplify-cli#9851](https://github.com/aws-amplify/amplify-cli/issues/9851) Damn... and for that reason we stayed away from using Amplify to manage...
> After following the steps provided by @soplan our app has encountered an error that occurs in different browsers for different users (which is strange) > > 502 ERROR The...
@hloriana this is also related to https://github.com/aws-amplify/amplify-hosting/issues/2846 so you can close this
> @gibron and @soplan could you please provide app IDs for apps still producing this behavior? arn:aws:amplify:eu-west-1:336514608551:apps/d2oqb1vmqxo34n