-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[SDK 45.0.1][expo-dev-client] No reconnect to Metro possible, blank screen after reload #17389
Comments
I think this is similar bug report? #17089 |
Might be related, indeed |
I think there may be deeper issues here possibly related to #17355. Do you see two "android bundling complete" when pressing
I'm also seeing that updated code is not loaded on the first reload, it takes 2 reloads. |
We've spent some time investigating this and haven't been able to reproduce what you're experiencing. If someone can take the time to put together a reliable repro case we can investigate further |
Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue. The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue. A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own. ResourcesCommon concerns"I've only been able to reproduce it in private, proprietary code"You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase. "I didn't have time to create one"That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template. "You can reproduce it by yourself by creating a project and following these steps"This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue. |
Several thumbs up but still got closed? |
Summary
SDK 45.0.1 and expo-dev-client 0.9.5 handled all the long lasting DX issues and crashes. Thanks a ton.
After upgrading, I found a small issue, which is a bit annoying:
I am not sure why expo-dev-client can't reconnect to Metro in first place. I am also handling WebSockets in my App which can recover after a day. It looks like there is no real integrated mechanism to try to reconnect to the running CLI instance.
I can just restart the App and everything is fine, but doing so I always lose my current state and can't test backgrounded scenarios correctly, because Metro connection is lost.
Managed or bare workflow? If you have made manual changes inside of the
ios/
orandroid/
directories in your project, the answer is bare!bare
What platform(s) does this occur on?
iOS
Package versions
0.9.5
Environment
Reproducible demo
None. Grab any with current dev-client and follow my steps.
Stacktrace (if a crash is involved)
No response
The text was updated successfully, but these errors were encountered: