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

yarn ios completes with "nothing to compile" #17

Closed
zkhalapyan opened this issue Oct 28, 2021 · 3 comments
Closed

yarn ios completes with "nothing to compile" #17

zkhalapyan opened this issue Oct 28, 2021 · 3 comments

Comments

@zkhalapyan
Copy link

  • I'm submitting a ...
    [ X ] bug report
    [ ] feature request
    [ ] question about the decisions made in the repository
    [ ] question about how to use this project

  • Summary
    Following the exact step by step guidelines on the readme page; yarn ios just ends with "nothing to compile" and doesn't open any apps.

You can actually call npm start and this will go with the launch sequence, but will show a blank page on Expo Go.

What's the appropriate command to run?

  • Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
@cawfree
Copy link
Owner

cawfree commented Oct 28, 2021

Hello, are you trying to open the application in Expo Go?

I think the message nothing to compile comes from Hardhat, indicating that your contracts have already been compiled, so this is probably a red herring.

@zkhalapyan
Copy link
Author

zkhalapyan commented Oct 28, 2021

Not sure what was going on, calling yarn ios now works 🤷‍♂️ I lost track of the sequence of things I tried, but I bet if you start from a clean init, you would hit the same problem. I am using Xcode 13 by the way, seems like they deprecated instruments and that's causing more RN problems right now.

@cawfree
Copy link
Owner

cawfree commented Oct 28, 2021

I'm going to close this issue because issues with launching is related to #19 (incompatibility with Expo Go) and I'd like to maintain the discussion there.

Just to clarify, the contracts/ directory is compiled when the project is first bootstrapped, so it is perfectly normal to see nothing to compile since we attempt to recompile whenever the application is launched.

This message is not associated with any of the behaviour in React Native.

@cawfree cawfree closed this as completed Oct 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants