Fix new Android emulator fail to start application #1703
Merged
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
|
👍 after rebasing and updating sha of common lib |
TsvetanMilanov
force-pushed
the
milanov/fix-new-default-android-emulator-fail-to-deploy-application
branch
from
b38a379 to
b307764
Compare
After updating the Android default emulator the CLI starts it and cannot deploy the application on it. This is caused by the change in the OK message after the net.connect(port) client connects to the emulator.
TsvetanMilanov
force-pushed
the
milanov/fix-new-default-android-emulator-fail-to-deploy-application
branch
from
b307764 to
e3bdaa5
Compare
Plamen5kov
deleted the
milanov/fix-new-default-android-emulator-fail-to-deploy-application
branch
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.
After updating the Android default emulator the CLI starts it and cannot deploy the application on it. This is caused by the change in the OK message after the net.connect(port) client connects to the emulator.