[Feedback]Unable to Create login UI - TypeError

[LeoSalemann]

Page: /start/getting-started/setup/q/integration/android

Feedback:

Followed procedures in Create login UI for react native, expo start fails.

Also Note: Page says https://docs.amplify.aws/start/getting-started/setup/q/integration/android, but I was actually in https://docs.amplify.aws/start/getting-started/auth/q/integration/react-native#create-login-ui

[aehwany]

@LeoSalemann
Hi, I’m currently working on this issue. I followed the procedure in Create login UI for react native and I wasn’t able to reproduce the fail on running expo start.
Can you please provide more information on the following:

• Can you provide more details on the system/environment you were using (ex: OS)
• I’m wondering if you were trying to setup an Android or React Native project using Amplify. I’m bit confused with the wording, since you mentioned Android, but you’re using the guide for react-native.
• Do you get the following errors in the screenshots when running expo start? The reason Im asking is because these errors are related to React.
• Can you please clarify on the last note you mentioned about wrong pages being displayed?

[LeoSalemann]

@aehwany

• I believe I was running a linux/ubuntu VM in Virtual Box, hosted on a Macbook running OSX 10.15.7
• I was setting up react native.
• I believe I was suing expo start
• To clarify, I was indeed running the react-native tutorial. When I ran into trouble and clicked the We'd Love your feedback link, the Page field of the issue got defaulted to :/start/getting-started/setup/q/integration/android when I was actually in /start/getting-started/auth/q/integration/react-native#create-login-ui.

Hope this helps.

[aehwany]

@LeoSalemann
Thanks for your feedback, I'm afraid I still have difficulty reproducing the issue you have encountered.
I followed your steps as specified,and got the following feedback page. As you can see, the path seems right here.
Please let me know, if I missed any step on reproducing your issue.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems.