fix(livesync): __onLiveSync function must be called on the UI thread#1108
Merged
mbektchiev merged 3 commits intoreleasefrom Mar 26, 2019
Merged
fix(livesync): __onLiveSync function must be called on the UI thread#1108mbektchiev merged 3 commits intoreleasefrom
__onLiveSync function must be called on the UI thread#1108mbektchiev merged 3 commits intoreleasefrom
Conversation
This was no longer happening after merging the fix for #1021
mbektchiev
force-pushed
the
bektchiev/livesync-in-main-thread
branch
from
1145065 to
3d1bfcf
Compare
vtrifonov
approved these changes
Mar 25, 2019
Uncomment `xcodebuild` build command of TestRunner before running `xcodebuild archive`
There's an issue with the linker paths to `libNativeScript.a`. Add `NativeScript` target as a target dependency and manually add the path to the library
ghost
removed
the
5 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 was no longer happening after merging the fix of #1021