Kddimitrov/fix splashscreen generation #4274
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…(allow debug + hmr in sidekick)
fix: fix unhandled promise rejection error from sidekick when livesync to preview app with bundle
…ed-event fix: allow Debug + HMR using the public API
… recreating it each time
fix: fix debugger attaching after a page reload
fix: fix stopApplication on Simulator while the app is on a breakpoint
… connection errors
fix: suggest manual app start instead of crashing on ios debug socket connection errors
…issue fix: require user interaction for developer disk image only in debug
fix(preview-publicApi): Add force option when getting the plugin's warnings
When preview is called with webpack from Public API, if you stop the livesync (via stopLiveSync method) while webpack is still working, in the output you'll see an error as webpack's child process exits with `null` exit code. However, this error does not have any meaning for the user, so we shouldn't raise it. Move the logging of the error to LiveSyncService's handler of `previewAppLiveSyncError` event - in the described case it will not be raised as LiveSyncService had already removed all listeners.
Currently the `previewAppLiveSyncError` event is handled only when CLI is used as a library. Add handler when CLI is used from command line and use the same workflow in both cases. Attach to the event every time when a new operation is started. Currently, once LiveSync is stopped, we've removed all handlers and we were never attaching them again. Now we rely on the isInitialized property, so we'll attach the event handler whenever it is needed.
…ew-stop fix: do not show error from preview initialization when stop is called
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
What is the current behavior?
SplashScreen generation fails for JS projects.
What is the new behavior?
SplashScreen generation succeeds for JS projects.
Fixes/Implements/Closes #4272