Closed cmaronchick closed 5 years ago
Ok, I figured this out. When I called Auth.createCognitoUser, it only calls for the username rather than the { Username, Pool } object. When I just provided the username, it all worked as expected.
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels or Discussions for those types of questions.
Platform: React Native Additional Details: Using Expo to develop
When utilizing the Facebook OAuth flow, calling setSignInUserSession crashes on iOS and causes a non-crashing warning on Android.
To Reproduce Steps to reproduce the behavior:
Expected behavior The user session should be set without issue and Auth.currentAuthenticatedUser() should return the Facebook user.
Actual Behavior On iOS, I receive this error: 'unrecognized selector sent to instance' was thrown while invoking multiSet on target AsyncLocalStorage with params ( ....LastAuthUser
Smartphone (please complete the following information):
Additional context Note that when I use aws-cognito-identity-js and use CognitoUser to create a user and a session, I do not receive an error.
However, when I then call Auth.currentAuthenticatedUser(), it says that no user is logged in. When I reload the app though, the Auth.currentAuthenticatedUser() identifies the user created with the CognitoUser method.
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.