Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't find variable: setTimeout in react-native #1235

Closed
shinnapatthesix opened this issue Jul 13, 2018 · 4 comments
Closed

Can't find variable: setTimeout in react-native #1235

shinnapatthesix opened this issue Jul 13, 2018 · 4 comments
Labels
investigating This issue is being investigated

Comments

@shinnapatthesix
Copy link

I got this error when run react-native in release mode

screen shot 2561-07-13 at 20 48 42

@jordanranz jordanranz added the investigating This issue is being investigated label Jul 13, 2018
@jordanranz
Copy link
Contributor

jordanranz commented Jul 13, 2018

Hello, thanks for submitting an issue. Could you please provide a bit more detail.

  • Are you using a starter project or your own project with Amplify?
  • Which version of aws-amplify are you using?
  • Which version of react-native are you using?
  • Which version of Node are you using (node -v)?

@ricsam
Copy link

ricsam commented Jul 19, 2018

I had the same issue, tried to reproduce it but it was really hard. I think it might have something to do with shared dependencies of amplify and appsync or it is some kind of race issue when installing the dependencies.

The solution for me was to remove the appsync dependencies from package.json, delete yarn.lock 😞, delete node_modules and reinstalling (yarn install). Thereafter I re-added the appsync dependencies and ran yarn install.

I was not able to consistently reproduce the error in a test repo so I think it might be some race issue when yarn installing 🤷‍♂️ or the order of calling yarn add ...

My yarn version is 1.3.2
react native version 0.56.0
amplify version 1.0.0
appsync version 1.2.1

@powerful23
Copy link
Contributor

Closing this issue. Feel free to reopen if you still have this issue.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
investigating This issue is being investigated
Projects
None yet
Development

No branches or pull requests

4 participants