Skip to content

Conversation

manueliglesias
Copy link
Contributor

No description provided.

Copy link
Contributor

@undefobj undefobj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One clarification on the two use cases

Copy link
Contributor

@undefobj undefobj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add clarification on:

  1. Still need to have User Pool/Identity pool in aws_exports
  2. Need to configure oauth key: Amplify.Auth.configure({oauth});
  3. Linking from expo: import { Linking } from 'expo';
  4. In the Cognito console, under URLs for App Client Settings they need to use the URLs that Expo/Metro bundler is hosting the app locally with - e.g. exp://192.168.46.139:19000/--/, http://localhost:3000/, https://myapp.com/. Also need to tell customers what to do in prod by linking to RN docs.
  5. Per other comment, explain the difference of the default hosted UI with hostedUISignIn prop vs building your own UI with social provider direct access.
  6. Document customProviderSignIn and urlOpener

@manueliglesias manueliglesias force-pushed the manuelig/hosted-ui-rn branch from 00e52b8 to 619e1dd Compare March 5, 2019 02:22
Copy link
Contributor

@undefobj undefobj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get this show on the road!

@undefobj undefobj merged commit 3a7cb5e into aws-amplify:master Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

amplify/js Issues tied to JS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants