Caleb Pollman

Hi @madan712 Can you please elaborate on your ask?

@bestickley The `AuthenticatorProps` interface is available for import from `@aws-amplify/ui-react`. Please open an another issue if there are more types you would like to see exported!

@andrei-zgirvaci The new React Native `Authenticator` is now in developer preview which allows for custom sign up attributes. Take a look at our docs for more info: https://ui.docs.amplify.aws/react-native/connected-components/authenticator/customization#form-field-customization

Hi @udeeshaIS You can achieve the addition of a subtitle on the `SetupTOTP` route by passing a using `Header` component. Documentation can be found [here](https://ui.docs.amplify.aws/react/connected-components/authenticator/customization#headers--footers)

> @calebpollman I wouldn’t classify it as a Gen2 vs Gen1 thing but more of Legacy vs Resource config issue: > > * Only happens when the Geo resources are...

Since the issue here appears to be with the `@aws-amplify/react-native` package, transferring this issue to the Amplify JS github repo

@KenSosa95 Was able to reproduce the issue in an expo project without using expo go and believe the root cause to be a missing React Native polyfill dependency. Can you...

@ivan-kiselev Going to transfer this issue over to our sibling team Amplify JS to see if they can unblock you with the Pinpoint/Cognito integration piece as analytic recording is not...

@rastoelias @storcswap Based on your comments here it sounds like a different issue than the issue @JoseeWouters is encountering as the projects are using Amplify Gen2 (rather than migrating from...

@JoseeWouters Apologies for the churn here. Transferring this issue over to the Amplify JS team for further triage since it reads as an issue with usage of NextJS App Router...