Cognito issue with Google and Apple

Since you're having issues with different providers, that suggests there is an issue on Cognito itself. I would suggest you: -Check Recent Changes: Even though you mentioned that no changes were made, it's worth reviewing any recent changes in the AWS environment that could affect Cognito. This includes changes in related services such as IAM roles, policies, or Lambda triggers associated with Cognito. -Review Attribute Mapping: In the Cognito console, review the attribute mappings for external providers to ensure that required attributes are correctly mapped from Google and Apple to Cognito user pool attributes. An empty list error might indicate an issue with the mapping configuration where Cognito expects certain attributes that are not being provided. -Examine App Client Settings: Verify the settings of your Cognito user pool's app client, especially the enabled identity providers and the attribute read and write permissions. Ensure that the configurations align with the requirements for using Google and Apple as identity providers. -Inspect Token Processing: If you have any Lambda triggers set up for pre or post-authentication processes, inspect the code to ensure that it's not modifying user attributes in a way that could lead to this error. The issue might arise if a Lambda function is incorrectly handling the attributes returned by the identity providers. -Test with AWS CLI or SDKs: Try to authenticate using the AWS Command Line Interface (CLI) or one of the AWS SDKs to see if the issue persists outside of your application environment. This can help isolate the problem to either the service or the application implementation. -Consult AWS Service Health Dashboard: Check the AWS Service Health Dashboard to see if any ongoing issues with AWS Cognito might be affecting its functionality. -Enable Logging: Increase the logging level for Cognito and monitor the logs in Amazon CloudWatch. This might provide more detailed insights into what's happening during the authentication process and why the error is being triggered.