-
Notifications
You must be signed in to change notification settings - Fork 62
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 doesn't launch expo server, leading to unhandled exception #19
Comments
When it refers to JSON RPC, it is failing to connect to a local hardhat node which is running a simulated local blockchain. It should get started by this line in your The warning you're seeing seems to indicate that although the application has bundled successfully, it is struggling to connect to the simulated blockchain where the example contracts will be deployed. This could be happening is because you're invoking the application directly as opposed to going through Can you please provide your console output? There might be an indication there that some tasks haven't initialized correctly. |
Here is the output for yarn ios:
Here is the metro node output:
|
Thanks for that! This looks okay (assuming that you opened and dismissed the QRCodeModal on launch), and appears to verify that the original issue was due to the hardhat node not being launched due to a manual invocation of the app. I'll keep this issue open since it seems like it'd be useful to initialize hardhat independently of |
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
Running on sim, so if the expo server is up and running localhost:8081 should resolve.
Updates:
package.json
, we can see what yarn ios is calling:"ios": "react-native run-ios",
. AFAIK this assumes that expo server is already running?expo start
and use the QR code to open it in Expo Go. Nope... this leads towards a blank screen 😡expo run:ios
that should launch the iOS app directly. Nope, this leads to the same issue.The text was updated successfully, but these errors were encountered: