fix: Connect to the next best realm if the Explore JumpIn fails (II)#867
Merged
sandrade-dcl merged 2 commits intomasterfrom Jul 29, 2021
Merged
Conversation
Contributor
|
After the CI passes:
|
sandrade-dcl
changed the title
D4rWiNSS
approved these changes
Jul 29, 2021
AjimenezDCL
approved these changes
Jul 29, 2021
This was referenced Jul 30, 2021
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
3 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.
What does this PR fix?
Fix #244
It is a second part of the previous PR (#781). We found an issue when we tried to re-joinning to the next best realms that was making it always failed. This PR fix it!
How to test the changes?
Our Code Review Standards
https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md