Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the error dialog we show when detecting bundle error.
Previously, we'd direct the users to app logs from that dialog. Those logs apparently never display any valuable information about bundling as they come from the app process, while bundle errors are reported by metro.
In addition, the reload button from bundle error would request JS reload, which isn't sufficient in the case when the app boots up with a bundle error.
We are therefore making the following changes:
restart
– restart implementation is smart enough and will attempt to reload JS when the app process is running, otherwise it will try to restart the app process, which is also good in case when we're recovering from initial bundle errorreload
implementation to remove "TODO" added there. The TODO was about handling unsuccessful reloads. Those could happen when the user forces "reloadJS" but the app process isn't running. In such a case we shouldn't attempt another reload method as that's not what user requested. Instead we will show an error popup with message that the reload attempt wasn't successful.How Has This Been Tested: