Restored Working Build of Android Emulator Container Scripts #345
+21
−217
Conversation
This file contains 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
…o the emulator's gRPC server on port 8554, making it impossible to see, hear, or interact with the emulator using the WebRTC or PNG views.
|
THank you! |
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.
Fixed the issue where Envoy wasn't routing requests from localhost:8080 to the emulator's gRPC server on port 8554, which made it impossible to connect to the emulator using both the WebRTC and PNG views in the React component. Now Envoy successfully routes requests to the gRPC server on port 8554 and the full functionality (e.g. seeing, hearing, sending GPS coordinates, etc) of the React component and container scripts has been restored, resulting in a working build of the container scripts.